Cowboy coding
From Wikipedia, the free encyclopedia
| This article's external links may not follow Wikipedia's content policies or guidelines. Please improve this article by removing excessive or inappropriate external links. (January 2009) |
| This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (June 2007) |
Cowboy Coding is a term used to describe software development where the developers have autonomy over the development process. This includes control of the project's schedule, algorithms, tools, and coding style.
A Cowboy Coder can be a lone developer or part of a group of developers with either no external management or management that controls only non-development aspects of the project, such as its nature, scope, and feature set. (The "what", but not the "how").
Cowboy Coding can have positive or negative connotations, depending on one's opinions on the role of management and formal process in software development; "Cowboy Coding" is often used as a pejorative term by supporters of software development methodologies, such as Agile.
[edit] Examples of Cowboy Coding
- How Adobe's Photoshop Was Born
- About Apache HTTP Server
- A brief history of Facebook
- Early history of Google
- The Graphing Calculator Story
- History of Linux
- The MySQL Story
- Switcher: The Macintosh's first multi-tasking environment
[edit] External links
- Cowboy Coder definition at Wards Wiki
- Delving into Cowboy Programming

