Programming

28157 readers

231 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Unethical Ways to Manage Technical Debt (queue.acm.org)

submitted 1 day ago by codeinabox@programming.dev to c/programming@programming.dev

22 comments fedilink hide all child comments

You can ignore it, tie it to unrelated company initiatives, or feign ignorance and simply not offer solutions that add to it. Or… you can adopt more above-board techniques such as Crawl/Walk/Run and the Reverse Farmer’s Rule, which reframe projects so that confronting tech debt is an upfront part of the plan.

you are viewing a single comment's thread
view the rest of the comments

[–] MonkderVierte@lemmy.zip 3 points 1 day ago (1 children)

Accrued brittleness.

[–] noughtnaut@lemmy.world 2 points 4 hours ago* (last edited 4 hours ago)

I really like the signalling here: "things might break unless we address it, and we did it to ourselves."

Or maybe "superfluous cost of ownership" to speak to the bean counters, but yours is way better.

Who are we kidding, "tech debt" is what we're stuck with. But have an upvote nonetheless.