3 ms·
What if the guy who takes 5X to do the work has less bugs and more efficient code and secure code? just because you code faster doesn't mean your code is better
by xenoterracide 19y ago
What if the guy who takes 5X to do the work has less bugs and more efficient code and secure code? just because you code faster doesn't mean your code is better, in fact it is probably worse, because you didn't take your time.
I'm merely saying that the speed you produce code is not directly related to it's quality. Release early and often does have it's merits. But that doesn't mean whip code out in an hour, and then fix bug after bug after bug.
- pchristensen 19y agoThat's the point (even inferable from the title) - he'd take a good programmer who was slow (like you describe) over the bad programmer, who is slow, and writes bugs, and takes a long time to fix those bugs, and makes more work for other people. Fast good programmer > slow good programmer > fast bad programmer > slow good programmer.
- jimbokun 19y ago"Fast good programmer > slow good programmer > fast bad programmer > slow good programmer." Got a cycle in your graph :).
- pchristensen 19y agoYikes. Let's try again. "Fast good programmer > slow good programmer > fast bad programmer > slow bad programmer." Looks like that makes me a "fast bad programmer". Not bad for third place.