News for hackers. Stuff that matters.

A comment on How to approach and prioritize technical debt. Parent comment

Re:How to approach and prioritize technical debt by thinkmassive on Monday January 31, 2022 @02:38PM (#30153121)
> The best way to deal with tech debt is to never use the term in the first place.

At the very least, give it a more specific name.

A Reforge article[0] that was shared here about a month ago[1] suggests these six categories:

  - maintenance debt
  - developer efficiency debt
  - stability debt
  - security debt
  - technical product debt
  - decision debt
[0] https://www.reforge.com/blog/managing-tech-debt

[1] https://news.ycombinator.com/item?id=29727487

[ Parent | on HN ]
Re:How to approach and prioritize technical debt by kahmeal on Monday January 31, 2022 @06:21PM (#30156256)
All this granular bullshit is entirely too much overhead and an unnecessary layer to "manage" imo. "Tech debt" and handling it should be part of your culture and by default included in the scope of any estimate that touches something affected by it. You negotiate out of addressing it, not into it.
[ Parent | on HN ]
Re:How to approach and prioritize technical debt by louwrentius on Monday January 31, 2022 @06:45PM (#30156521)
%s/debt/bugs/g

Really the concept doesn’t add anything.

[ Parent | on HN ]