This thing with duty feeling is hard. They all feel they did their best. Exactly as my precursor who spend 17 years in the role and did way below bare minimum. No single comment in the code. Last project does not work at all, but was approved as finished. Laziness and ignorance are everywhere. As long as managers accept it there is no way to stop that. Maybe I should stop drawing flowcharts in ascii art manner. Nobody will say “thank you” for that anyway. Nobody will give me a raise for that. It might help the next guy in my chair, but should I care about him?
> This thing with duty feeling is hard. They all feel they did their best
If you work in aerospace and your "best" is non-redundant inputs from a sensor known to fail, you're not good enough for aerospace and never were. I know not to do that and I'm just a former SRE who also likes air crash investigation. My homelab has more redundancy than a critical system that could by design crash an airplane.
And people at Boeing knew this. That's why they hid the system's existence from everyone and lied to the FAA, who also utterly failed at doing its job.
I heard this was done on purpose because they'd need a lot more documentation if the system was important, and having redundancy would tip off the FAA to its importance.
