[jacobsenscott]

I don't know if I've seen "tech debt" do serious damage to any company, and I've been around a long time. I've definitely seen whole teams grind to a halt in pursuit of someone's idealized vision of the "perfect way to organize code" though. They always couch it in the language of tech debt, but really it's just the loudest person's preferred way to shuffle files around - and usually in the direction of more complexity and not less.

[techpression]

Proving a negative and all that. I’ve definitely seen it do crazy damage, features that should take a week takes six months and turn out to need another year of fixing. But that’s the easy part, the hard part is how it affects culture and how the skilled people leave because they’re severely underutilized.

So when some people talk about tech debt we don’t talk about perfect code or file structure, it’s about painting a wall in a tropical rain, building a house during an earthquake etc. So count yourself happy I guess.

[bojan]

> I don't know if I've seen "tech debt" do serious damage to any company, and I've been around a long time

Just to provide a counter data-point, I've certainly seen companies not being able to move anymore because of tech debt. It's not for nothing that so much has been written about it, and about the ways to fix it.

Your other point stands - the resume-driven development is also a real problem.