As a data engineer, testing with production loads is critical to performance checking, as well as finding edge cases where your assumptions about what can be expected in the data are curb stomped and send you back to the drawing board to cry and think about what you’ve done.
Yeah we finally set up a workflow where we get production data available in a staging environment. This has saved a lot of trouble via “well it worked on my local where there were 100 records, but prod has 1037492 and it does not”
deleted by creator
As one of the devops/sysadmin types, if we give access to prod data to preprod systems, they are now in audit scope and you have to harden them or we lose our insurance and compliance certs.
Obviously the solution is to build some system where everything works out, but it’s not as easy as “just give root to devs”.
I have three setups DEV: an environment that is almost useless thanks to how many changes have to be made between production and the development environment.
TEST: A More useful exact cloan of production that you still have to edit specific things but it is usually the same each time.
PROD: this one just never works right.
I’ve definitely had the experience of something being broken in Prod… and no one can reproduce it in Dev.
Guess where we are fixing it!?
A coworker once got an HR talking-to for printing this meme out and leaving it on all the dev’s desks.
Regardless of the meme, it’s just weird behaviour to print off a meme, in presumably tens of copies, and leave it on every desk. Don’t you have a group chat?
