Comment Re:Why? (Score 1) 425
When I write relatively large pieces of *new* code, I work in distinct phases.
One phase is thinking, planning and generally percolating ideas. This can go on for weeks as I work out the the design. I might not physically interact with a computer much, preferring pads of paper and office toys.
At some point I hit a point where things "click" and I can envision the full system's operation in sufficient detail.
The next phase is typing. This can on for some time too depending on the size of the system. At this point, I generally listen to loud techno, industrial, etc and my "coding" task essentially *is* data entry, whether I am typing in unit tests or actual implementation code.
There are of course other phases, but the point of calling out these two is that there are processes whereby subby's typing speed might not affect his/her final quality.
Typing speed does matter here, and generally does not affect the quality of the finished product.