You must log in or register to comment.
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.
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.
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.
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.
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!?
Sounds like a fun project
My customer does this bullshit. Every time: “We can’t deploy that necessary/required update because we haven’t tested it yet. Also, we have no testing environment and we need that update to fix a serious problem. This is all your fault.”
