222
Incident Postmortem (programming.dev)
submitted 2 years ago by 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
[–] 4 points 2 years ago (2 children)

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
    •
  • [–] 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 1 child comment
    •
  • [–] 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