> You'd never see a civil engineer or most any other engineer operate under the "move fast and break things" philosophy.
Because people will die. Software engineers who, say, work in the airline industry don't do this either (they also probably use ada or something like it).
I'd also be willing to bet a significant amount of money that an engineer that works on something like soft drink bottles moves a lot faster than one who designs bridges.
Exactly: there's no one true way, there's just the acceptable tradeoffs.
Which is the proposal I tend to write the most when businesses send a requirement my way: "X is important. Ensure X." - whatever X is, you can usually then pretty quickly outline how to do X perfectly, and how much X will cost, and suddenly there's an acceptable degree of X (which is usually outlandishly far below the implied standard of the original request) because as it turns out, they simply didn't think X had any real cost associated with it.
Because people will die. Software engineers who, say, work in the airline industry don't do this either (they also probably use ada or something like it).
I'd also be willing to bet a significant amount of money that an engineer that works on something like soft drink bottles moves a lot faster than one who designs bridges.