_boardwalk

Car analogies (and generalizations in general) are not so useful.

I've seen many cases (and been frustrated) working in a corporation where high levels of caution end up creating much more total work to make changes incremental. And when you do finish, the code is often not is nice as if it had been all done at once (at which point it probably gets left as is as more important things than refactoring, in the eye of business people, come along).

Relevant TED talk: http://www.ted.com/talks/lang/en/steven_johnson_where_good_i... Basic idea is that open-ended collaboration > working alone. Which doesn't so much conflict with the idea that working alone > working on a "committee" or "team", in my opinion.