221
Incident Postmortem (programming.dev)
submitted 2 months ago by riskable@programming.dev to c/programmer_humor@programming.dev
11 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] abbadon420@lemm.ee 23 points 2 months ago

I don't get it

[-] XEAL@lemm.ee 26 points 2 months ago

I had to look it up.

It's like an evaluation or restrospective analysis that you do after an IT incident has taken place, like all company servers being down for hours.

So I guess the joke here is that the guy has lost almost all his hair due to the stress of the incident.

[-] riskable@programming.dev 9 points 2 months ago

Correct 👍

[-] snugglebutt@lemmy.blahaj.zone 4 points 2 months ago

I'm drunk but maybe you're troubleshooting some crap and pulling your hair out because of it..

[-] wewbull@feddit.uk 3 points 2 months ago

Oh, "incident post-mortem" was ambiguous. I read "Incident that happened after death" not "analysis after incident".

I thought OP had a necrophiliac blowjob fantasy.

[-] sheogorath@lemmy.world 2 points 2 months ago

In software development it’s usually used to describe the situation after an incident was resolved. The team that’s responsible for the feature usually performs a postmortem to find out the root cause and find out what they can do to avoid another incident.

this post was submitted on 24 Aug 2024
221 points (96.6% liked)

Programmer Humor

19529 readers
397 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev