Dimensions
234 x 184 x 20mm
The first guide to the growing idea of 'software debt', examining the tension between speed and perfection in shipping software. Software debt is the concept that it is okay to ship software knowing that there is still some 'not-quite-right' code in it. It shows the importance of dealing with the 'debt' of that code as quickly as possible. By writing the code knowing there will be quick revisions, developers can ship needed software faster, meeting their organization's needs better. The idea of software debt is a relatively new one among developers, and one that is rapidly gaining momentum. The basic concept is that shipping a new application is like going into debt. A little debt speeds development as 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.