4 ms·
Jeff likes to give his posts misleading titles. Iteration (which is what he's referring to when he says "quantity") is an essential part of quality software. B
by henning 18y ago
Jeff likes to give his posts misleading titles.
Iteration (which is what he's referring to when he says "quantity") is an essential part of quality software. But "quantity over quality" suggests perpetually producing lots of crap without regard to outcomes.
Still, his call to prefer working, shipping code over paralysis-through-analysis is very good.
- stcredzero 18y agoActually, the preference for Iteration is really just another form of "Evolution is Smarter Than You." Or, if you will: You'll never learn as much about [X] by just thinking about it, as opposed to actually doing [X] a whole bunch! (While thinking about it.)
- michaelneale 18y agoAn interesting counterpoint (kind of anyway): http://ravimohan.blogspot.com/2007/04/learning-from-sudoku-solvers.html http://ravimohan.blogspot.com/2007/04/learning-from-sudoku-s...
- stcredzero 18y agoBut that is Doing & Thinking vs. Doing & not enough thinking. Our options are: 1) Too much thinking, not enough doing 2) Balanced thinking & doing 3) Too much doing, not enough thinking As often is the case, the middle path is best.
- michaelneale 18y agoYes I agree, its not a terribly interesting conclusion, but a balanced approach wins (at least for interesting problems). I guess there is often a risk that there is too much thought/talk versus action more so then the reverse (not to say that the reverse doesn't happen, it is just rarer).