[thejeff]

Well, in theory there are such people. Software engineers, system designers, etc. Some of the larger and more critical software systems actually use them. And go through rigorous testing processes. Medical software, avionics controls, things like that.

There is a big difference between software and disciplines like architecture and engineering though. Writing software is more analogous to the design phase of building projects. It's much easier to modify code, no matter how badly designed than to modify an existing building. That's why you have to design for future expansion when your working with the physical world. It may be difficult to modify the code, you may even have to rewrite completely, but that's nothing compared to rerouting a highway.

More cynically, from what I've seen, most programmers are taught at least the basics and theory of design. Algorithms, design patterns, layers, etc. Then they get a job and the money people just want something that works, as quickly and cheaply as possible. This is particularly true of any kind of retail software. It gets sold based on features and maybe a quick demo, not on how sound the codebase is. If the first version doesn't sell, there won't be a second, so why spend time and money designing for it?