There's a neat part of the article that might better demonstrate what I'm talking about.
---
> Because I was young, super-anal, and wasn't on SSRIs back then, I once asked Carmack why he didn't use libraries for common functions that he could share between engine revisions. Carmack's a super-nice guy, but on this one instance he used the "Well, I think my methods work pretty well..." defense. I never suggested coding style changes again.
> But, really, for him it made no sense to share code, because, like a bee, it was just as fast to write new code. The template was in his head, he types really REALLY fast—why bother importing something?
> Don't take this to mean his code was spaghetti—it was actually some of the easiest-to-understand code I've ever worked with. It has an almost indescribable quality of "obviousness." Like, you know when a really good teacher explains something, it seems obvious? That's what his code was like. I mean, OF COURSE there's a loop where you service the pending events and call a refresh on the UI layer.
The bottleneck in programming lies in designing something that works correctly, understanding someone else's design or legacy code, designing test cases, debugging problems, addressing performance issues. It is a brain-bound problem, unrelated to motor skills.
I have never thought "this project would have succeeded if only everyone on the team had been a faster typist!"
On the other hand, when we are on the same page, slow typing is seldom a problem.