220

Incident Postmortem (programming.dev)

submitted 3 weeks ago by riskable@programming.dev to c/programmer_humor@programming.dev

11 comments fedilink hide all child comments

top 11 comments

sorted by: hot top controversial new old

[-] abbadon420@lemm.ee 23 points 3 weeks ago

I don't get it

[-] XEAL@lemm.ee 26 points 3 weeks 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 3 weeks ago

Correct 👍

[-] Panties@lemmy.ca 7 points 3 weeks ago

Same

[-] XEAL@lemm.ee 2 points 3 weeks ago

Here's my take

[-] snugglebutt@lemmy.blahaj.zone 4 points 3 weeks ago

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

[-] wewbull@feddit.uk 3 points 3 weeks 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 3 weeks 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.