2 ms·
There's a saying that aviation regulations are written in blood: https://aviation.stackexchange.com/questions/13081/why-do-people-say-aviation-regulations-are-w
by pavel_lishin 8y ago
There's a saying that aviation regulations are written in blood: https://aviation.stackexchange.com/questions/13081/why-do-people-say-aviation-regulations-are-written-in-blood https://aviation.stackexchange.com/questions/13081/why-do-pe...
After every airplane crash, there's a major post-mortem. The root causes are ferreted out, as deeply as possible, in a blame-free way - and the regulations are updated and followed by the entire industry, enforced by laws.
What happens when your system has a 30 minute downtime? There's a meeting, someone suggests running your code through a linter or bumping log levels or adding another unit test, everyone high-fives and you wait until the next downtime - and that institutional knowledge doesn't leave the company, sometimes not even the team. Sometimes, it barely registers with the team members, who then quit the company and go and write voting software.
Part of it is that our industry is still relatively young - although, not that much younger than the aviation industry. But a bigger part is that for the most part, it's very strongly segmented, and most of those segments aren't responsible for people's lives.