October 07, 2016

This is part one of a two-piece post that I have planned on technical debt. Tech debt accrues in various ways; you build products fast and make short-term decisions that hurt your product’s long-term stability and maintainability. Sometimes, a conscious decision to take on debt is made in order to hit an important deadline or reach a market position. In some cases, lack of experience and adhering to best practices could leave you with a huge mess on your hands.

>Read the source article at dzone.com

Related Resources:

The Phenomenon of Technical Debt - The technical debt metaphor is gaining quite a bit of traction in the software development world. This term was coined by American Ward Cunningham in a report at the OOPSLA conference (Object-Oriented Programming, Systems, Languages & Applications, an annual ACM research conference) in 1992; he said, "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...

Technical Debt, Legacy Code and the Internet of Things - Software used to be seen as something that could be written once and used many times with ever "breaking down." However, that illusion faded when problems began to appear, ultimately caused by continual development without the correct quality control process in place.

Posted under
Software Testing News