571
Developer stages of grief
(kbin.melroy.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Mar 2024
571 points (98.1% liked)
Programmer Humor
32386 readers
1005 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
What if you're the one that was in charge of adding safe guards?
Never fire someone who fucked up (again; it isn’t their fault anyways). They know more about the system than anyone. They can help fix it.
This is the way usually but some people just don't learn from their mistakes...
If you are adding guardrails to production... It's the same story.
Boss should purchase enough equipment to have a staging environment. Don't touch prod, redeploy everything on a secondary, with the new guardrails, read only export from prod, and cutover services to the secondary when complete.
Sorry, not in budget for this year. Do it in prod and write up the cap-ex proposal for next year.
Yeah right? Offset via the cortisol of developers