Revision as of 18:42, 19 August 2017 edit 2a01:4c8:40d:2294:2e22:7528:279d:af39 (talk) →Advantages: Edited to remove negative inference that this applies only to hobbyists. Tags: Mobile edit Mobile web edit ← Previous edit		Revision as of 20:20, 19 August 2017 edit undo 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 Next edit →
Line 7: }} {{Use mdy dates\|date=February 2016}} '''Cowboy coding''' is a [[software development]] ~~methodology~~ 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.{{Citation needed\|date=January 2011}} 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