Cowboy coding: Difference between revisions

Revision as of 21:45, 25 February 2010

Revision as of 21:46, 25 February 2010

Line 11:

==== Lack of release structure ====

TheLack project may lack a [[feasibility study]],of [[estimation (project management)|estimation]], or implementation planning may cause a project to be delayed. Sudden deadlines or pushes to release software may encourage the use of [[quick and dirty]] or [[code and fix]] techniques that will require further attention later.

==== Inexperienced developers ====

Cowboy coding is common at the hobbyist or student level where developers may initially be unfamiliar with the technologies, such as the [[build tool|build tools]], that the project requires. This can result in time required for learning to be underestimated, causing delays in the development process. Inexperience may also lead to disregard of accepted [[Standard_Operating_Procedure#Information_technology_industry_use|standards]], making the project source difficult to read or causing conflicts between the [[Semantics#Computer_science|semantics]] of the language constructs and the result of their output.