Cowboy coding: Difference between revisions

Revision as of 10:55, 7 February 2024

Latest revision as of 04:24, 13 August 2025

(One intermediate revision by one other user not shown)

Line 2:

{{multiple issues|

{{procon|date=July 2013}}

{{POV|date=July 2013}}

{{refimprove|date=January 2011}}

{{original research|date=January 2011}}

Line 36 ⟶ 35:

* It allows developers to cross architectural and/or tiered boundaries to resolve design limitations and defects.

* As discussing architectures, writing specifications and reviewing the code all take their time, a single developer (if sufficient) may well produce a working application faster by cowboy coding. Tasks like research or prototyping may not require the code quality more complex methods provide.

* Since coding can be done during the developer's free time, a project could come to fruition which otherwise wouldn't have.<ref>K, Alex. [httphttps://googleblog.blogspot.com/2006/05/googles-20-percent-time-in-action.html "Google's '20 percent time' in action"], Official Google Blog, May 18, 2006</ref>

==See also==