570
Developer stages of grief (kbin.melroy.org)
you are viewing a single comment's thread
view the rest of the comments
[-] fidodo@lemmy.world 51 points 9 months ago

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

[-] YtA4QCam2A9j7EfTgHrH@infosec.pub 40 points 9 months ago

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.

[-] raldone01@lemmy.world 14 points 9 months ago* (last edited 3 weeks ago)

This is the way usually but some people just don't learn from their mistakes...

[-] bane_killgrind@lemmy.ml 5 points 9 months ago

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.

[-] meat_popsicle@sh.itjust.works 9 points 9 months ago

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

[-] bane_killgrind@lemmy.ml 3 points 9 months ago

Yeah right? Offset via the cortisol of developers

this post was submitted on 02 Mar 2024
570 points (98.0% liked)

Programmer Humor

32706 readers
300 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS