Programmer Humor

32561 readers

390 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

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

569

Developer stages of grief (kbin.melroy.org)

submitted 8 months ago by devilish666@lemmy.world to c/programmerhumor@lemmy.ml

29 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] fidodo@lemmy.world 51 points 8 months ago (2 children)

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

[–] YtA4QCam2A9j7EfTgHrH@infosec.pub 40 points 8 months ago (1 children)

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 8 months ago

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

[–] bane_killgrind@lemmy.ml 5 points 8 months ago (1 children)

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 8 months ago (1 children)

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 8 months ago

Yeah right? Offset via the cortisol of developers