No piece of code is written in isolation - the interdependencies are there and real. Think twice about features no one requested, because it could very well bite you right when it comes time to implement the features everyone knows they want!
Technical debt is any unaddressed opportunity to improve a codebase. If a non-programmer asked though, how would you explain it? Here's 10 ways I might try.
Just completed the “Understanding and Eliminating Technical Debt” course by Mark Heath on Pluralsight. What is technical debt? I would imagine most of the I.T. community has heard of “technical debt” by now. The term originated about 20 years ago with Ward Cunningham. He was trying to explain to