Cowboy Coding Article Index for
Cowboy 		Shopping
Coding 		Website Links For
Cowboy 		 

Information About

Cowboy Coding
  CATEGORIES ABOUT COWBOY CODING
   
software development philosophies
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...



As with all methodologies, the skill and experience of the user(s) define the degree of success and/or abuse of such activity. The greater the controls and/or checks and balances systematically imbedded within a process, offers stronger levels of accountability of the user(s). It is the degradation of well intended procedures which lead to activities often defined as Cowboy coding.

Both lightweight and heavy weighted methodologies of today still lead to this breakdown as the user(s) attempts to facilitate within social/political environments within organizations. The probability of this breakdown can be directly correlated to the degree of processes inhibiting the risk of user(s) deviating from the organization standard, however at the potential cost of efficiency.

The ideology of Software Development Best Practices has established a fervor of religious debates.

Disadvantages:

  • Lacks a clear scope and vision. The project sponsors will have no clear idea that their objectives have been communicated with the developer.

  • Encourages a lack of visibility in the code. Poor coding can be hidden, as there is nobody to review it. This leads to developers who believe that as long as the code works it's good enough, and consequently it becomes difficult or impossible to maintain.

  • Only suitable for small projects. Projects that require a high degree of complexity will begin by showing fast progress, but then become bogged down as the developer finds adding more functionality to the codebase increasingly difficult.

  • Poor quality software. With no Code Review , Pair Programming , Unit Testing , release testing or other quality mechanism cowboy coding tends to produce buggy software.

  • Doesn't scale well. If there is more than one programmer there needs to be some mechanism for them to organise the development. At this point even small teams will document and organise the project in some form.

  • Lack of Version Control . Cowboy coding will often ignore other industry best practises, such as using a version control system. Since cowboy coders often work alone they see no point in the overhead of a version control system.


Advantages:

  • Allows for quick solutions for small problems. Often a problem is small enough and well understood enough that documentation and planning are overkill. Typically when the job is going to take a day or two, and involve only a single developer.

  • Can allow a 'spike' to see if a programming idea is valid before embarking on a larger project that depends on the idea. A spike is where you write a small proof of concept application to prove that a method is valid. These applications generally do not form part of a real finished application.

  • Can be used by students to learn more about programming in general, and to explore problem domains. Generally businesses will not be willing to pay for this kind of exercise in a commercial setting.


Other Similar Methods:

Cowboy coding; often used as a diminutive term, has been confused with other software development methodologies which have solved the issues surrounding cowboy coding. Extreme Programming for example also does not emphasise documentation. However Extreme Programming does use methods to document user requirements and guide the software development team. It also addresses code quality through unit tests and peer review, and is thus quite different.

Agile Development 's frequent reevaluation of plans, emphasis on face-to-face communication, and relatively sparse use of documents sometimes cause people to confuse it with cowboy coding. Agile teams, however, do follow defined (and often very disciplined and rigorous) processes, something that distinguishes agile approaches from cowboy coding.