3 ms·
"The sooner you start to code, the longer the program will take." I certainly benefit from regular reminders of this.
by japhyr 12y ago
"The sooner you start to code, the longer the program will take."
I certainly benefit from regular reminders of this.
- agumonkey 12y agoI'm a little stumped by that, I'm all for repl oriented development, ~zero round trip time etc etc but I have to admit that when you thought the problem through in your head long before writing any, then the right code will fall through. So are instantaneous cycles good or bad ?
- mattrepl 12y agoInstant feedback makes coding more tangible but can be harmful. One may get caught in an edit-eval cycle and spend time solving the wrong problem. Regularly stepping back and reevaluating assumptions/goals helps. (And write supporting tests, if you swing that way.)
- japhyr 12y agoFor me this advice is about developing your spec to an appropriate level of detail before writing any significant amount of code. I'm still in the phase where writing code is fun, and it takes a little discipline to think my spec through enough to make my code-writing time efficient.
- apricot 12y agoSo are instantaneous cycles good or bad ? Three pounds of flax.
- contingencies 12y ago(price of) To the extent that [Agile software development] is [an excuse for not thinking], it's a bad thing. - Leslie Lamport