Comment by polskibus
10 years ago
I believe the author has mistaken speed with efficiency. What's the benefit of being fast if you're sloppy and have to redo things often?
10 years ago
I believe the author has mistaken speed with efficiency. What's the benefit of being fast if you're sloppy and have to redo things often?
The implied benefit is that repetition improves quality, so more repetitions, more quickly, means your quality will improve more quickly.
You need to self-reflect after each iteration, mind you, to make sure that you learn each time you do the thing. But, this is necessary for skill progress whether you're going fast or slow.
(And, having to make the corrections can be as informative or more so, depending on how you're able to reflect on the "why" you're refining or fixing the thing).
"The implied benefit is that repetition improves quality, so more repetitions, more quickly, means your quality will improve more quickly."
Yes, but that's frequently not the case. Developers at "sweat shops" tend to write far more code, and work many more hours, than the average dev at a top tier software house and yet they are usually much worse devs.
That's largely (IMO) because those sweat-shop developers started out as much, much worse devs, whose only viable option was a sweat-shop.
The claim is that repetition and a short feedback/learning cycle will improve a developer more quickly than a long cycle. It doesn't say that a poor developer with a fast cycle will out-learn a different, stronger developer with a slow cycle.
>> You need to self-reflect after each iteration, mind you, to make sure that you learn each time you do the thing. But, this is necessary for skill progress whether you're going fast or slow.
I feel a tendency towards perfectionism is implied by the tendency toward slowness. Working quickly could balance out the most self-defeating aspects of perfectionism.