You are viewing a single thread.
View all comments View context
51 points

What if you’re the one that was in charge of adding safe guards?

permalink
report
parent
reply
40 points

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.

permalink
report
parent
reply
14 points

This is the way usually but some people just don’t learn from their mistakes…

permalink
report
parent
reply
5 points

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.

permalink
report
parent
reply
9 points

Sorry, not in budget for this year. Do it in prod and write up the cap-ex proposal for next year.

permalink
report
parent
reply
3 points

Yeah right? Offset via the cortisol of developers

permalink
report
parent
reply

Programmer Humor

!programmerhumor@lemmy.ml

Create post

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.

Community stats

  • 4.9K

    Monthly active users

  • 1.6K

    Posts

  • 36K

    Comments