Revision as of 22:25, 3 March 2022 edit Rswelker (talk \| contribs) 26 edits Added citation. Tag: Reverted ← Previous edit		Revision as of 05:27, 4 March 2022 edit undo 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 Next edit →
Line 10: '''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. 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").~~<ref>~~{{~~cite web~~Citation needed\|~~last1=Welker \|first1=Scott \|title=What is Cowboy Coding? \|url=https://www.techslang.com/definition/what-is-cowboy-coding/ \|website=Techslang \|publisher=Techslang \|access-~~date=~~3 March~~January ~~2022~~2011}}~~</ref>~~ "Cowboy coding" commonly sees usage as a [[pejorative\|derogatory]] term when contrasted with more structured [[software development methodology\|software development methodologies]].

Cowboy coding: Difference between revisions