Time-to-market is the only valid argument for writing crap code and not unit tests. I'm not sure if you can seriously argue with economic reasons when talking about testing. The most costs in software development arise in the operations/maintenance phase and are probably (there are much papers on this topic) multiple times higher than the costs of the implementation phase.

I agree that every software development team has to make their own decision to balance development time and maintenance cost but I don't agree with this low entitlement mentality of writing correct code in this article.

Of course there are also costs when implementing tests and your unit tests are rendered useless on design changes. But so what? You're also decreasing code assurance and it's better to increase it with tests so that you won't encounter bugs in production which is much more expensive than writing tests.

Software development is not only about adding functionality but also about ensuring its correctness.