If lack of a feature will force you out of business today it doesn’t matter how much it will cost to deal with the code tomorrow; you must do the best you can in the time you have. Making this kind of design compromise is like borrowing time from the future and is known as taking on technical debt.
- Chapter 1. Object-Oriented Design
- from Practical Object-Oriented Design in Ruby: An Agile Primer
- Publisher: Addison-Wesley Professional
- Released: September 2012
definition of technical debt
Share this highlighthttp://www.safaribooksonline.com/a/practical-object-oriented-design/69198/