>But its a solvable problem I would push back a little bit that this is the sole reason (and thus not quite as solvable a problem as one might think). A couple

>But its a solvable problem I would push back a little bit that this is the sole reason (and thus not quite as solvable a problem as one might think). A couple other reasons that help explain why a lot of software sucks: 1) Unlike other engineering disciplines, there is not strict adherence to codified standards. It's easy for me to argue that my solution is adequate, even when if yours may be objectively better. An electrician or civil engineer has much less leeway for creativity because they are constrained by codes, standards, and industry-accepted best practices where adherence/compliance is culturally ingrained. Software, by comparison, is very much the Wild West. 2) It's very easy to change. Because software is relatively easy to change, it means configurations are often less stable. Especially at scale (and combined with the lack of standards), this can cause problems. 3) It's relatively cheap to implement (superficially at least) and there's a low barrier for entry (superficially at least). Software doesn't have the culture of other engineering disciplines regarding accreditation. I'm not a huge fan of credentialism personally, but it can provide a stop-gap in terms of skills, especially when those doing the hiring don't know how to properly assess those skills.