> Clearly the developer(s) didn't have a clear idea of how to design software and abstract it into pieces that are independent and reusable. Is this not often

> Clearly the developer(s) didn't have a clear idea of how to design software and abstract it into pieces that are independent and reusable. Is this not often the case because you have people that are not actual developers involved in the process of software creation? In the sense of, you don't get budget to fix/refactor something because business says so; you have to make your app comply with some shitty legacy standard because business wants to have your software work with some stuff from 20 years ago - and so on, the list is basically endless. Don't get me wrong, developers (myself included) are probably more than enough at fault themselves, but if 'creating software' was only about making nice, clean, awesome code that really does what it's supposed to do, devs in general would probably make a better work out of it compared to what is happening in the real world - where non-dev people also have a say in what/how you create software.