First, I believe wanting to fix broken windows and technical debt is everyone's goal. The author mentions a couple of times that fixing technical debt is just a

First, I believe wanting to fix broken windows and technical debt is everyone's goal. The author mentions a couple of times that fixing technical debt is just a stacks' preference. I disagree with that. Not least because fixing technical debt can sometimes take quite a lot of time and boring, error-prone work - not quite the stuff of heroic tales - but also because I have seen many examples in my career of technical debt created by people wanting to hack something together quickly, and then never getting around to cleaning it up, leaving all sorts of surprises behind them. I think generally it's good thorough thinking that gets rid of technical debt (see, e.g., Rich Hickey's work, and his Hammock Driven Development "methodology"). Generally, I'm sorry, but chasing the quick-fix is immature, and a sign of a desire to please. That is completely normal, and it's healthy to let off steam through a quick fix now and then. But the "stack" model here sounds to me more like what happens in my head when I procrastinate... IMO for a project to succeed someone will ultimately have to keep track of what is done. Do you want to be that person, or do you want someone else to do it while you get lost in your stack overflows?