That’s why we have 4 environments, development, test, pre-production and production.
Test only on dev hardware because production hardware is too expensive to waste on developers. No idea why the software runs better on dev hardware than production. They’re kind of similar.
Testing is a sign of weakness.
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.
And then managers that don’t get this will try to shove policies down our throats about how “pre-prod systems should not have access to prod data”.
“just obfuscate it.” Sure, for all 300Tb of it from the 10 different sources that don’t really talk to each other and we were already doing magic to be able to join them together? They should give us a bottle of hard liquor per month/project.
You misspelled gallon(s).
17 years working with hospital patient data. I’m going to curl up in a corner and cry now…
dev teams usually :
What’s the worst that could happen,people won’t die
this guy :
17 years working with hospital patient data
must be high pressure work.
You test in dev? You mean you don’t have a Q&A environment? or staging?
I test my own code/scripts in dev when I’m working on it. QA usually tests acceptance criteria in test environment. And then staging is used for production data testing for performance and identifying missed edge cases. Actually, we sometimes use dev and test interchangeably when multiple people are working on the same repo, so the lines are a little blurrier than that.
Heh, loads.
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!?
That’s why it helps to have a staging environment as well.
Jeez bud just laugh at the meme for fucks sake
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.
“as above, so below”
If your test and prod are different, you need to ensure your manager understands the risks you will not magically account for. It’s on their head when it fucks up.
Testing in prod requires its own separate indemnification because that’s also only ever after direct orders.
I prefer camel case
Sounds like a fun project
