Real engineering failures instead of success stories(failhub.substack.com)
failhub.substack.com
Real engineering failures instead of success stories
https://failhub.substack.com/p/failhub-issue-1
10 comments
Agree and the site here is too high level without insight. An open, good list of post mortems might be more helpful [1]. Just an addition, Code Smells [2] are a useful addition to patterns.
[1] https://github.com/danluu/post-mortems [2] https://blog.codinghorror.com/code-smells/
[1] https://github.com/danluu/post-mortems [2] https://blog.codinghorror.com/code-smells/
was earnestly hoping for something a little more in depth than "we never solidified the requirements" and "complexity is bad" which are both quite widely understood
I was excited about this idea, but based on the writing patterns and vague stories I'm pretty sure these writeups are mostly AI slop. For example, this is classic ChatGPT phrasing:
> The growth I’d been celebrating wasn’t real growth—it was just a spike of first-time buyers who never came back.
If I'm wrong, and these were actually written by a human, I'd love a chance to stand corrected and apologize.
> The growth I’d been celebrating wasn’t real growth—it was just a spike of first-time buyers who never came back.
If I'm wrong, and these were actually written by a human, I'd love a chance to stand corrected and apologize.
I suspect they were developed (maybe AI-written) by a human, but the same human.
There's little variety in the way the stories are told.
I suspect that it will be tough to get folks to add to it, but it's not a bad idea.
One site I regularly visit, is Not Always Right[0]. I suspect that many of the stories are apocryphal, but it is entertaining.
I really miss the US Navy Safety Photo of the Day. That was a riot.
[0] https://notalwaysright.com/newest/
There's little variety in the way the stories are told.
I suspect that it will be tough to get folks to add to it, but it's not a bad idea.
One site I regularly visit, is Not Always Right[0]. I suspect that many of the stories are apocryphal, but it is entertaining.
I really miss the US Navy Safety Photo of the Day. That was a riot.
[0] https://notalwaysright.com/newest/
Whether or not it's AI written, these very vague stories are not useful.
To find slop in this submission, you don't have to look any further than the very first picture.
Back issues of Game Developer used to have post-mortems of major projects, both successful and unsuccessful. Those were concrete. This is vague and abstract.
Flying magazine has been publishing "I learned about flying from that" since 1939, and those articles are still good.
Flying magazine has been publishing "I learned about flying from that" since 1939, and those articles are still good.
#2 is very crucial and it's something I've learned has to be well defined. Just this past week I heard a task was done. I check it. Only half is done. They didn't check the issue ticket before asserting completion. Not a big deal but it does mean I should walk through that when we start tickets next time.
Some more great engineering failures are here ;
https://stream.engineered.network:8002/stream
https://stream.engineered.network:8002/stream
One criticism I have though is that documenting a failure doesn't mean you actually realized what truly went wrong and even if you accurately describe what went wrong that doesn't mean you have a real solution to that problem. Often the reason things went wrong were far more nuanced and the fix is not obvious. Adding an untested lesson at the end of each of their failures is premature. I'd call them, at best, observations and next steps to try. They are only lessons after they have truly been tested and successfully navigated around the original failure.
[1] https://en.wikipedia.org/wiki/Anti-pattern