World Library  
Flag as Inappropriate
Email this Article

Cowboy coding

Article Id: WHEBN0002088387
Reproduction Date:

Title: Cowboy coding  
Author: World Heritage Encyclopedia
Language: English
Subject: Design, Amateur film, Freeware, Indie art, Indie design
Collection: Software Development Philosophies
Publisher: World Heritage Encyclopedia

Cowboy coding

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. 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").

"Cowboy coding" commonly sees usage as a derogatory term when contrasted with more structured software development methodologies.


  • Disadvantages 1
    • Lack of release structure 1.1
    • Inexperienced developers 1.2
    • Uncertain design requirements 1.3
    • Incompleteness 1.4
  • Advantages 2
  • See also 3
  • References 4
  • External links 5


In cowboy coding, the lack of formal software project management methodologies may be indicative (though not necessarily) of a project's small size or experimental nature.[1] Software projects with these attributes may exhibit:

Lack of release structure

Lack of estimation or implementation planning might cause a project to be delayed. Sudden deadlines or pushes to release software may encourage the use of quick and dirty or code and fix techniques that will require further attention later.

Inexperienced developers

Cowboy coding can be common at the hobbyist or student level where developers might initially be unfamiliar with the technologies, such as testing, version control and/or build tools, usually more than just the basic coding a software project requires.

This can result in time required for learning to be underestimated, causing delays in the development process. Inexperience might also lead to disregard of accepted standards, making the project source difficult to read or causing conflicts between the semantics of the language constructs and the result of their output.

Uncertain design requirements

Custom software applications, even when using a proven development cycle, can experience problems with the client concerning requirements. Cowboy coding can accentuate this problem by not scaling the requirements to a reasonable timeline, and might result in unused or unusable components being created before the project is finished. Similarly, projects with less tangible clients (often experimental projects, see independent game development) could begin with code and never a formal analysis of the design requirements. Lack of design analysis could lead to incorrect or insufficient technology choices, possibly requiring the developer to port or rewrite their software in order for the project to be completed.


Many software development models, such as Extreme Programming, use an incremental approach which stresses that the software must be releasable at the end of each iteration. Non-managed projects may have few unit tests or working iterations, leaving an incomplete project unusable.


  • Developers maintain a free-form working environment that may encourage experimentation, learning, and free distribution of results.
  • It allows developers to cross architectural and/or tiered boundaries to resolve design limitations and defects.
  • Without a development/designer framework, the programmer, as opposed to the project manager, is responsible for removing roadblocks. This might improve the speed of development.
  • Independent developers can begin projects with cowboy coding techniques before later selling them to commercial use or creating community-supported projects.
  • Small projects might be burdened by heavy software management methodologies; cowboy coding removes this burden.
  • Since coding can be done during the developer's free time, a hobby project could come to fruition which otherwise wouldn't have.[2]

See also


  1. ^ Hughes, Bob and Cotterell, Mike (2006). Software Project Management, pp.283-289. McGraw Hill Education, Berkshire. ISBN 0-07-710989-9
  2. ^ K, Alex. Google's "20 percent time" in action Official Google Blog, 2006-5-18

External links

  • Cowboy Coder definition at Wards Wiki
  • Cowboy Coding definition at Wards Wiki
  • Delving into Cowboy Programming
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from World eBook Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.