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.
I mean, that is fine and all about the historical reasons we dont have engineer titles, but the OP comment was gatekeeping one part of IT from another like there was an actual legal distinction between a dev, someone in infrastructure or someone in support.
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.
I mean, that is fine and all about the historical reasons we dont have engineer titles, but the OP comment was gatekeeping one part of IT from another like there was an actual legal distinction between a dev, someone in infrastructure or someone in support.
There is not.
I mean there is distinction between software engineers and software developers as far as the degree