Content deleted Content added
No edit summary |
m →Advantages: HTTP to HTTPS for Blogspot |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 2:
{{multiple issues|
{{procon|date=July 2013}}
{{refimprove|date=January 2011}}
{{original research|date=January 2011}}
Line 8 ⟶ 7:
}}
{{Use mdy dates|date=February 2016}}
'''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. Typically, little to no coordination exists with other developers or stakeholders.
Line 23:
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 underestimating time required for learning, causing delays in the development process. Inexperience might also lead to disregard of accepted [[Standard
===Uncertain design requirements===
Line 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. [
==See also==
| |||