| ▲ | sho_hn 3 hours ago |
| I understand there's been drama, and someone walked away or was pushed out. I don't quite care enough to understand it all or point at guilty parties. However, my current understanding is that the project remains active, so titling this article "Post Mortem" feels a bit like it's done in bad faith as it's usually applied to projects that are over. It's certainly what I immediately assumed made it newsworthy. |
|
| ▲ | hiccup_socks 2 hours ago | parent | next [-] |
| >"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 2 hours ago | parent | next [-] | | 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. | | | |
| ▲ | kevinrineer 2 hours ago | parent | prev | next [-] | | > ... 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 2 hours ago | parent [-] | | >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" |
| |
| ▲ | sho_hn 2 hours ago | parent | prev [-] | | 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. |
|
|
| ▲ | jovial_cavalier 2 hours ago | parent | prev | next [-] |
| Antheas was the #1 most active developer, and responsible for almost all low level integrations. |
| |
| ▲ | bee_rider 2 hours ago | parent | next [-] | | Just based on this blog post it seems like he wanted the project to be more “professional” in some way that the rest of the developer group didn’t. I wonder if that difference in vision, combined with a (probably justified based on your comment) feeling that he was doing a disproportionate amount of the work lead to an unsustainable situation. Calling it a post-mortem while others are continuing the project still seems kind of petty, though. | |
| ▲ | sho_hn 2 hours ago | parent | prev | next [-] | | Software history is rife with projects that outlive a person like that leaving, though. Ulrich Drepper comes to mind immediately. They don't own the project. | |
| ▲ | aprilwaters an hour ago | parent | prev [-] | | Nope, he was not, and his software will be replaced. | | |
|
|
| ▲ | Forgeties79 3 hours ago | parent | prev | next [-] |
| As a bazzite user who had no idea anything was up until this headline, yes that was very concerning at first glance |
|
| ▲ | 0xedd 2 hours ago | parent | prev [-] |
| [dead] |
