I might be out of this site moto, but.. Just my IMHO - If customer's business processes can not be described by clean code this means business process is messe

I might be out of this site moto, but.. Just my IMHO - If customer's business processes can not be described by clean code this means business process is messed up itself. And if client want to ship it now and do not care if it is right - process is broken. I think this comes from the world of proprietary software, where agencies write some mess code to fit exactly current business practices and continue to "iterate" with this mess patching ad-hoc new and new requirements from executives. This leads to huge overhead in software. The only reason we do not see all this disgusting shit - it is proprietary. This approach is good for agency. And sometimes - for client. But not for all of us. I am talking about banking/law/health/etc systems built with exact ideas represented in this article. In open source world such approach simply will not work. Nobody will want to touch junk spaghetti code. So... I believe this approach flawed in long run. And we as developers should be more then stupid machines producing code. We need to think forward and if something do not make sense - tell it and push through if needed. just some random rant after seeing boss pushing project which kinda fits client's business schema, but then it starts stagnate, 'cos it require more changes... And these changes lead to even more mess..