Cowboy coding: Difference between revisions

Content deleted Content added
Reverted 2 edits by 2601:C6:8303:2AF0:87D:B7FE:6604:BC9F (talk): Unsupported. (TW)
Tag: section blanking
Line 17:
===Lack of release structure===
Lack of [[estimation (project management)|estimation]] or implementation planning might 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 can be common at the hobbyist or student level where developers might initially be unfamiliar with the technologies, such as testing, version control and/or build tools, usually more than just the basic coding a software project requires.
 
This can result in time required for learning to be underestimated, causing delays in the development process. Inexperience might 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.
 
===Uncertain design requirements===