203
Your Engineers Aren't Lazy, Your Codebase Is Punishing Them
(piechowski.io)
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 31 Mar 2026
203 points (99.5% liked)
Programming
27035 readers
305 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
Well, yeah - that never happens. You do tech debt cleanup "as you go". Slip in a few tickets to cleanup specific things and have a policy to update code that is touched when adding features / fixing bugs.
It needs to be a continual cleaning process. That's why it's called debt - the longer you let it go un-paid the harder it is to do.
I suggested at my current job that we adopt a policy of fixing things as we go. Boss wasn't interested. He said his boss said "he doesn't want people gold plating things".
Okay. I guess we'll keep this tower of bash scripts that breaks once a month.
Isn't it for the team to find out and decide whether they reached "gold plating" yet? That statement doesn't sound like a rejection or reason for rejection to me.