[hiccup_socks]

>"Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over.

is it? outside of autopsies, i think i have only ever seen it used as a synonym for "incident report". i dont think ive ever associated the term specifically with the end of a project.

e.g. cloudflare uses the tag for all of their incident reports (https://blog.cloudflare.com/tag/post-mortem/), not as a signal that they are closing shop

[throwaway_ocr]

In the incident case, it's a post-mortem on the incident. The incident itself is (hopefully) resolved and can now be dissected to learn about what went wrong and how things can improve in the future.

That's what a post-mortem implies to me in the tech industry. A thing happened, it's over now, here are the lessons we learned to take into the future.

[sho_hn]

Yes, but Bazzite is not over.

[sho_hn]

Gamasutra has a famous line of articles where game developers provide retrospectives on how the development of their titles went, maybe I'm influenced by that.

I'm aware about the use in incident reports of course, but then you still don't call it "<project name> Post-Mortem" but use a more specific namespace.

[kevinrineer]

> ... as a synonym for "incident report"

People should stop using it as a synonym, then. The Latin effectively means "after death", meaning its a poor synonym for "what happened wrong recently".

[hiccup_socks]

>The Latin effectively means "after death"

language evolves over time

post mortem is even in dictionaries (meriam, oxford, american heritage) as "an analysis or review of a finished event"