Cowboy coding: Difference between revisions

Revision as of 15:58, 2 November 2010

Revision as of 13:00, 16 December 2010

Line 1:

{{External links|date=January 2009}}

'''Cowboy coding''' is a term used to describe 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.

Line 30 ⟶ 28:

* By coding in their own time, a hobby project may come to fruition which otherwise wouldn't have<ref>K, Alex. Google's "20 percent time" in action http://googleblog.blogspot.com/2006/05/googles-20-percent-time-in-action.html, Official Google Blog, 2006-5-18</ref>.

* It allows truly talented developers the license they need to maximize their potential. {{Citation needed|date=September 2010}}

== Examples of cowboy coding ==

{{POV-section|date=September 2009}}

* [http://web.archive.org/web/20070717193315/http://siliconuser.com/?q=node/10 How Adobe's Photoshop Was Born]

* [http://httpd.apache.org/ABOUT_APACHE.html About Apache HTTP Server]

* [http://www.guardian.co.uk/technology/2007/jul/25/media.newmedia A brief history of Facebook]

* [[History of Google#Early_history|Early history of Google]]

* [http://www.pacifict.com/Story/ The Graphing Calculator Story]

* [https://netfiles.uiuc.edu/rhasan/linux/#New%20Baby%20in%20the%20Horizon History of Linux]

* [http://blogs.sun.com/TechDaysEvents/entry/the_mysql_story The MySQL Story]

* [http://folklore.org/StoryView.py?story=Switcher.txt Switcher: The Macintosh's first multi-tasking environment]

== External links ==