You know why you can do that? Because you have hindsight. You see exactly where the business went. And this is the same damn trap all neophyte developers fal

You know why you can do that? Because you have hindsight. You see exactly where the business went. And this is the same damn trap all neophyte developers fall into. "Let's rewrite!" Once that first wave of business requests and demands comes along, your precious sandcastle will crumble. Because the business team is fickle. And they stick you with deadlines. And then, mid-deadline, they change their mind. Or are forced to go a different direction because some shit government law is passed that requires you to broadcast your service requests with encrypted messages tied to pigeons (because, realistically, that's how the government does APIs). Here on the internet where everything is made up and the points don't matter, you can get away with rewrites. Agile not working for you? Let me introduce you to the CADT model (http://www.jwz.org/doc/cadt.html http://www.jwz.org/doc/cadt.html). All rewrites become tomorrow's bug-infested legacy ghettos.