Code and fix
From Wikipedia, the free encyclopedia
 |
This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (July 2007) |
Code and fix development is not so much a deliberate strategy as an artifact of schedule pressure on software developers. Without much in the way of a design, programmers immediately begin producing code. At some point, testing begins (often late in the development cycle), and the inevitable bugs must then be fixed before the product can be shipped. Detractors of agile programming methodology claim that it is an apologist acceptance of code and fix, though the setting of periodic goals (iterations or sprints) help differentiate it.
