Ouch! Yes, that can happen, and I'd argue it's pathological. Let me rephrase that series of events as follows:
1. Artificial deadline is set.
2. Artificial deadline is unnecessarily converted into crucial deadline.
3. Code quality suffers, saddling the company with technical debt that costs real money and real opportunities later.
> many of the deadlines are baked into the contracts as deliverables
Oh absolutely. I'm a consultant too, and I do that all the time. I set my contractual deadlines such that I don't have to sacrifice the codebase. Granted, there are exceptions to every rule, and I'm not going to claim I've never, ever accrued technical debt due to a deadline. But I wouldn't make it a philosophy, which the article seems to be doing.