Programming

28153 readers

209 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

20 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

[–] DementedSociety@lemmy.world 4 points 21 hours ago (1 children)

It is the VERY CONCEPT of technical debt! Shortcut after shortcut shortcut... The company is literally shortcuts all the way down. No left at the company even knows how to work the erp properly. Because the person who set it up and customized it didn't document or train anyone and then left... Technical debt. How about the mountain of product SKUs that were forced out the door never properly tested, filled with bugs and zero documentation... Left of the next guy... Technical debt. What about all those products not having real assembly or test documents and there being a literal single guy that knows how to test and program everything? No way to pass that info on besides a mountain of manufacturing engineering work? Technical debt.

What are you talking about dude!?!? Lolol.

[–] lysdexic@programming.dev 1 points 15 hours ago (1 children)

No left at the company even knows how to work the erp properly. Because the person who set it up and customized it didn’t document or train anyone and then left…

That's not technical debt. That isn't even the definition of legacy code. That's a mess and a whole set of problems, but technical debt ain't one of it.