221
Incident Postmortem (programming.dev)
submitted 3 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
[-] snugglebutt@lemmy.blahaj.zone 4 points 3 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 3 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 3 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

19623 readers
1 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