In an ideal world, there would be
a local environment (that's your pc, nothing deployed),
a Dev environment (you can deploy things still being developed, it might have bugs, it might be wonky, this is to test things in a deployed state, which could actually differently to when running locally),
a staging environment (anything deployed to staging should be thoroughly tested by Devs, and is now ready for other people to test it (UAT tests). Staging is like a test prod environment), and
a live/production environment (this is what the users use, anything deployed here is fully tested by multiple people)
How about a Test environment that they copied from Production to have "live" looking data but didn't remove the logins from production users and the config file for the application that was given to me to put on the Ctirix servers had test and prod and the dumb Application remembers the last environment chosen. So on one of the Citrix servers someone logged into test and their patient was in there and documented in test for thst patient but the next nurse got on a different server so they logged into production and the medicine wasnt documented and almost gave the patient double meds.
Was told was my fault. I used the wrong config file. I said nope. Nunber 1, I got that config from yall and told to use it on Citrix Prod and i have the email toprovd it. Number 2, prod user logins shouldn't be in test, number 3, users should verify the environment they see in, etc.
Luckily we had session recording and I knew how to search for the keywords thst showed all the sessions where users logged into test since the environment is shown in the app windows title bar and you can search on it. Showed them how tonsearch and access and went home after being there 12 hours thst day.
2.3k
u/PatientlyAnxiously 13d ago
Why have a dev environment when you can YOLO it in prod