I don't know that there are many people in industry who can't code or who don't care. I think there are lots of people who may not share in the peculiarities of

I don't know that there are many people in industry who can't code or who don't care. I think there are lots of people who may not share in the peculiarities of my opinions, or who need every minute to deliver requirements, and who feel that "working" is sufficient. Is that wrong? I'm hesitant to say that it is. We're optimizing different things. Their approach is better in some situations - startups need to ship features fast, and if you don't have to touch the code again, it doesn't need to look good, it just needs to work. My method is optimized for sustaining engineering by adding up-front engineering time, which startup engineers may not have. I think the most appropriate thing is to realize what situation you're in, and make value judgements there. If speed is required, optimize for speed. If sustainment is required, optimize for sustainment.