Winsights.life

Ok- i think we need to pause this until we come up with more structure. I love that we are actually beta-testing the beta-testing process. That will be a priority to discuss next week. I think we need to pause for now- This is from Sid:

I wanted to make a small but important suggestion regarding how we handle testing across both applications.

From my experience, testing with personal or real user IDs tends to create downstream complexity especially when it comes to data segregation, cleanup, audits, and future migrations. Over time, it becomes difficult (and sometimes risky) for database admins to reliably distinguish real data from test data if testing isn’t done using clearly designated test identities. (attaching an example of how it is stored in our system)

To avoid that path early, I propose we standardize on assigned testing IDs only for all testing and validation work. I’m happy to create and provision a set of test accounts (say ~10) that are used strictly for testing purposes across environments.

This will put us on a much cleaner and safer footing as the system evolves, particularly given the compliance and data-governance expectations we’re designing for.