> Sweden. Use of different rulers by builders caused the Vasa to be more heavily built on its port side and the ship's designer, not having built a ship with two gun decks before, overbuilt the upper decks, leading to a design that was top heavy. Twenty minutes into its maiden voyage in 1628, the ship heeled to port and sank.
On a side note - many of these are good samples of technical writing. They introduce the audience to the environment where failure occurred, but in a way that doesn't take the focus away from the issue itself.
At least one of these is just terrible. The “Facebook” one is written by some firm trying to hawk their monitoring stuff. It implies you can understand what happened inside from glorified traceroutes.
What actually happened that night is far more complicated, and has nothing to do with people intentionally disconnecting the site from the internet.
Can we also get some behind-NDA/service desk post mortems? IBM, Oracle Cloud, MuleSoft, Salesforce, etc. Having to submit a fucking service request to know why your business stopped running is a PITA.
17 comments
[ 2.0 ms ] story [ 58.6 ms ] threadThanks!
August 2015 (17 comments) https://news.ycombinator.com/item?id=10028353
January 2019 (1 comment) https://news.ycombinator.com/item?id=18875834
And the announcement blogpost: http://danluu.com/postmortem-lessons/
I don't know if this belongs in the list. xD
You can still modify the HN url to see that by removing the path.
If you do partial paths on other domains it doesn’t seem to work.
https://web.archive.org/web/20201010054131/https://news.ycom...
What actually happened that night is far more complicated, and has nothing to do with people intentionally disconnecting the site from the internet.
https://news.ycombinator.com/from?site=github.com/danluu