@yosh
@mcc
@blyxyasAlejandra Gonzalez I definitely had some "unwrap bad" thoughts at the beginning of this (although much more nuanced than that) but in addition to the somewhat rust-specific things I've learned as a result of the Discourse, I've also realized that there's a big plane-with-holes.jpg problem here: when a significant software system outage involving errors has occurred, the error-handling mechanism of the programming language it's written in will be implicated, regardless of how good it is
@glyph
@yosh
@blyxyasAlejandra Gonzalez I mean I thing the problem is more insidious than this-- in a failure analysis with many steps, there will be a tendency to focus on the simplest thing that appears in the failure chain, whether or not it actually failed in this case, because it's the one thing everyone can have an opinion on. It's a special case of the bikeshed principle
If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/mcc/statuses/115583655739573853 on your instance and quote it. (Note that quoting is not supported in Mastodon.)