Comment by MattPalmer1086

As an addendum, I've been on both sides of this argument. When I became the chief technical architect for a software company, I had to tell my colleagues to build a huge pile of crap to hit important commercial milestones and keep customers happy.

I pointed out that the total cost of doing this badly, then unwinding it and doing it properly would be at least double the total cost of just doing it right.

That didn't matter. We had to hit those goals. So that's what we did. It was expensive, buggy and kept us in business. My colleagues finally understood I had turned to the dark side :)