News for hackers. Stuff that matters.
Re:Whatever works by icebraining on Monday November 07, 2011 @12:59PM (#3207363)
Although immature code may work fine and be completely acceptable to the customer, excess quantities will make a program unmasterable, leading to extreme specialization of programmers and finally an inflexible product. 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, object-oriented or otherwise.

Ward Cunningham (http://c2.com/doc/oopsla92.html)

See also, Technical Debt (http://en.wikipedia.org/wiki/Technical_debt).

Re:Whatever works by brlewis on Monday November 07, 2011 @04:43PM (#3208308)
The point of the debt analogy is to communicate that it's something long-term undesirable, although it can be a short-term expedient. Where the analogy falls short is that real debt almost always has to be repaid. In a startup searching for product-market fit, the opposite true re. technical debt.