DEV Community

loading...

Discussion on: What have you found most difficult about prioritizing paying down technical debt in your software company?

Collapse
thawkin3 profile image
Tyler Hawkins Author

Can you point to specific examples of a bug that was introduced or a deadline was missed due to working in code that needs a refactor? Even better, can you assign a value to it? Perhaps down time in the app from a bug, developer hours (which ultimately == $$)?

That's excellent, gathering some data to show the financial cost to the business due to existing technical debt. I think that goes a long way, especially for upper management.

Collapse
aaronm14 profile image
Aaron Mead

Yup. You can roughly log how long it took you to fix a bug or how many bugs were created as a result of a change and multiply that by an average hourly or daily rate a company is paying for a developer. Especially if it impacts multiple developers!