Revision as of 20:20, 19 August 2017 edit Walter Görlitz (talk \| contribs) Extended confirmed users, Pending changes reviewers 294,571 edits →top: it's not a methodology at all, it is a negative practice ← Previous edit		Revision as of 12:41, 16 September 2017 edit undo 212.85.80.85 (talk) less ambiguous sentence structure Tag: Visual edit Next edit →
Line 22: 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 ~~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.<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===

Cowboy coding: Difference between revisions