Cowboy coding: Difference between revisions

Content deleted Content added
No edit summary
case fix
Line 8:
}}
{{Use mdy dates|date=February 2016}}
 
'''Cowboy coding''' is [[software development]] where programmers have [[autonomy]] over the development process. This includes control of the project's schedule, languages, algorithms, tools, frameworks and coding style. Typically, little to no coordination exists with other developers or stakeholders.
 
Line 23 ⟶ 24:
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 underestimating time required for learning, causing delays in the development process. Inexperience might also lead to disregard of accepted [[Standard Operatingoperating Procedureprocedure#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.<ref>{{cite web|url=http://www.stickyminds.com/presentation/stareast-2000-confessions-recovering-coding-cowboy|title=StickyMinds - STAREAST 2000: Confessions of a (Recovering) Coding Cowboy|work=StickyMinds|accessdate=February 2, 2016}}</ref>
 
===Uncertain design requirements===