Technical debt is the accumulation of a series of poor design choices--or poor implementation of good design choices--that makes ongoing maintenance and future changes more difficult than need be.
Common Sources of Technical Debt
Listed below are several common sources of technical debt. I'll explore each one in more depth in future articles. Links will be added accordingly.
- Old code left in place
- Old fields left in place
- Denormalized database tables
- Coding before designing
- Overuse of global state
- Overly clever code