Programming grew up in an environment where failure is cheap (relatively speaking). You might make a mistake that costs five, six, or even seven figures (I’m sure I’ve made at least one seven figure mistake), but nobody will die from it. When people could die, such as flight control software, different development techniques for formal methods are used. Those tend to cost at least ten times more than other methods, so they aren’t used much otherwise.
If anything, we should lean into this as an advantage. Iterate even faster, catch failures faster, and fix it faster.
surewhynotlem@lemmy.world 8 months ago
It’s exactly this. No one complains when IT infrastructure engineers design and build systems and call themselves engineers, even though they don’t have a PE certification. So if they can do it, why not support staff?