80
Unethical Ways to Manage Technical Debt
(queue.acm.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Aug 2026
80 points (97.6% liked)
Programming
28165 readers
312 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
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
I sometimes add a "tax" to the estimates of unrelated tasks, and use the extra hours to work on tech debt, unbeknown to upper management.
Not particularly ethical on my side, but... I'm the one that gets paged when things break down at night or on weekends, and I don't care that upper management doesn't care about that.
Ah, good old guerilla development
Is it really unethical if it benefits the organization? Even if that's not really the goal.
The blogger acknowledge that the use of the word "unethical" as a hyperbole ton drive engagement.
The real-world issue is that we need to get stakeholders on board with the idea of having to do extra work that is not required to deliver a feature. If you tell a manager that you need to spend a month rewriting a system that was just launched, they will laugh at you.
Refactor first to make the work easy, then do the work.