> There's nothing more permanent than a temporary fix.

That should be one of those Tech culture “laws.”

I suspect that the dependapocalyse is a significant factor. When every part of an operation has multiple context rebuilds, and resources are not shared across module boundaries, you get inefficient behavior.

But I’m skeptical that there’s a will to rethink that.

Totally agree. In these days of fast devs it's common to see PO's excitement reducing deadlines and assumimg a dev can deliver 5 feats in a day instead of trying to stabilize and fix bugs. Sad

Honestly, after years of seeing this play out, a lot of devs really lack the judgement to know when something is good enough to deliver and will endlessly delay projects to “ do the right thing”

No deadline, no product.

Shipping is very important, sometimes more important than what you ship :)

In my experience, many of those deadlines are commonly the only reason the company continues to exist as well.

The root of the problem is much more deeply ingrained in our economic system.