Hacker News new | ask | show | jobs
by z3t4 2857 days ago
I write down every issue - everything from user interface issues to bugs, and then delete them as they get fixed. I can then use that file to measure code debt. The file is saved in version control, so no fancy stuff, but I can run statistics and compare code growth and growth of issues. In my experience you want to keep this file small. On a current project I've estimated that it will take five years to clear this file <grin>. This file seem to grow exponentially with new features. And I think at some point there's a point of no return - where you can't possible fix all issues ...