Technical Debt is an interesting metaphor. Its been around now almost 25 years. This word was originally coined by the programmar Ward Cunningham who is also the one who developed the wiki software. His explanation of Technical debt is:
"Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite... The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt. Entire engineering organizations can be brought to a stand-still under the debt load of an unconsolidated implementation"
Here is a video of Ward Cunningham discussing about this:
All technical debt is not bad. To some extent, incurring some technical debt speeds up the software development process.
Here is another interesting write-up by Martin Fowler on Technical debt.
"Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite... The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt. Entire engineering organizations can be brought to a stand-still under the debt load of an unconsolidated implementation"
Here is a video of Ward Cunningham discussing about this:
All technical debt is not bad. To some extent, incurring some technical debt speeds up the software development process.
Here is another interesting write-up by Martin Fowler on Technical debt.
No comments:
Post a Comment