▲ 222 ▼ Incident Postmortem (programming.dev) submitted 2 years ago by riskable@programming.dev to c/programmer_humor@programming.dev 11 comments fedilink hide all child comments
[–] abbadon420@lemm.ee 23 points 2 years ago (3 children) I don't get it permalink fedilink source hideshow 6 child comments replies: [–] XEAL@lemm.ee 26 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] riskable@programming.dev [S] 9 points 2 years ago Correct 👍 permalink fedilink source parent [–] Panties@lemmy.ca 7 points 2 years ago (1 child) Same permalink fedilink source parent hideshow 2 child comments replies: [–] XEAL@lemm.ee 2 points 2 years ago Here's my take permalink fedilink source parent [–] snugglebutt@lemmy.blahaj.zone 4 points 2 years ago (1 child) I'm drunk but maybe you're troubleshooting some crap and pulling your hair out because of it.. permalink fedilink source parent hideshow 2 child comments replies: [–] wewbull@feddit.uk 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] sheogorath@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] XEAL@lemm.ee 26 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] riskable@programming.dev [S] 9 points 2 years ago Correct 👍 permalink fedilink source parent
[–] Panties@lemmy.ca 7 points 2 years ago (1 child) Same permalink fedilink source parent hideshow 2 child comments replies: [–] XEAL@lemm.ee 2 points 2 years ago Here's my take permalink fedilink source parent
[–] snugglebutt@lemmy.blahaj.zone 4 points 2 years ago (1 child) I'm drunk but maybe you're troubleshooting some crap and pulling your hair out because of it.. permalink fedilink source parent hideshow 2 child comments replies: [–] wewbull@feddit.uk 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] sheogorath@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] wewbull@feddit.uk 3 points 2 years ago (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [–] sheogorath@lemmy.world 2 points 2 years 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. permalink fedilink source parent
[–] sheogorath@lemmy.world 2 points 2 years 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. permalink fedilink source parent
