News for hackers. Stuff that matters.
Re:Reframing Tech Debt by nerdponx on Sunday November 21, 2021 @07:40PM (#29301334)
> Not in my experience! I think one can do pretty well a) refusing to put debt in to begin with, and b) for any new work, including necessary cleanup of what you'll be touching in the estimates.

My experience has been that, once in a while, even this is not enough. You might just get accused of being a perfectionist or being overly meticulous about things that don't matter, and why can't we just do it the easy way and worry about it later?

Of course, if that does happen, it means that you are in a toxic work environment and you need to leave as soon as you can. But it does happen, and I have experienced it firsthand.

Re:Reframing Tech Debt by secondaryacct on Sunday November 21, 2021 @08:10PM (#29301559)
But you missed his point, it can be negotiated too. You get called a perfectionist because you project you refuse compromises, but have you thought of the business cost of any quality-oriented delay? (the opposite of quality-oriented work is result-oriented work)

Yes doing shit on top of shit will be paid later, but sometimes, maybe that's fine to pay later while you are scrambling to make money in the first place ?

Re:Reframing Tech Debt by manquer on Sunday November 21, 2021 @11:51PM (#29302883)
Manytimes you just get replaced in the project, when you stand your ground on security or debt.

It takes time for well maintained project to detoriate bad end enough for debt to impact business.

Even when it does , both the biz and new tech leaders are likely to refuse to acknowledge debt is important factor or blame it on you or start a rewrite without understanding what is going wrong to build on top of some shiny new tech everyone wants on their resume.

Re:Reframing Tech Debt by wpietri on Monday November 22, 2021 @04:18PM (#29311673)
Sure! I definitely get that. And then you have to have the conversations with stakeholders about why best practices are actually best. And those conversations have to be had in business terms. E.g.: https://www.infoq.com/news/2010/03/code-quality-cost-mapping...

It's also possible to be both meticulous and flexible. Sometimes when I've gotten that "can we worry about it later" question, I'll tell them yes. If we have a big external deadline or something, I'm happy to treat tech debt like a high-interest credit card. We run up the bill in an emergency, and then as soon as the emergency's over, we pay off the credit card.