Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

technical debt is not always a "bad thing". Sometimes it makes sense to rapidly iterate until you understand what it is that needs to live on. If the risk for not getting the code out exceeds the risk for whatever technical metric is going to be improved by addressing the technical debt, then by all means iterate.


If technical interest rates are dirt low on your technical debt, go into technical debt. :)


Loved how that was framed. I'm going to start assessing the interest rate. Which to me is the interest leadership has on fixing vs new features.


Or, to stick with the analogy more closely; what is interest? It's the cost of servicing a debt. Technical debt has a low cost to the extent that it Just Works. If it has to be constantly propped up, then it's high interest.


For instance, there is no point in refactoring a piece of code that never needs maintenance. In that case it is good debt and it already paid off.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: