Code and fix

Code and fix development is not so much a deliberate strategy as an artifact of schedule pressure on software developers^[1]. 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^{[citation needed]}.

See also

• Software engineering
• Wikibooks:Computer programming

Notes

References

• McConnell, Steve. "7: Lifecycle Planning", Rapid Development. Redmond, Washington: Microsoft Press, 140. 

This software engineering-related article is a stub. You can help Wikipedia by expanding it.