Revision as of 05:27, 4 March 2022 edit Walter Görlitz (talk \| contribs) Extended confirmed users, Pending changes reviewers 294,571 edits Undid revision 1075097015 by Rswelker (talk) not a reliable source. This entry has no author and while the site has an editorial policy, there is no posted editorial team. Tag: Undo ← Previous edit		Revision as of 16:29, 1 November 2022 edit undo 2600:1700:6435:f000:d191:b57:88f6:49d4 (talk) No edit summary Next edit →
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. A cowboy coder can be a lone developer or part of a group of developers working with minimal process or discipline.<ref>{{cite web \|last1=Scott \|first1=Welker \|title=cowboy coding \|url=https://searchsoftwarequality.techtarget.com/definition/cowboy-coding \|website=searchsoftwarequality \|publisher=TechTarget \|access-date=2 March 2022}}</ref> Usually it occurs when there is little participation by business users, or fanned by management that controls only non-development aspects of the project, such as the broad targets, timelines, scope, and visuals (the "what", but not the "how").{{Citation needed\|date=January 2011}}

Cowboy coding: Difference between revisions