3 ms·
I enjoyed the read. > If you compare two coders, one who can touch type and one who has to hunt and peck, the difference between them is not just down to typin
by ChrisMarshallNY 5y ago
I enjoyed the read.
> If you compare two coders, one who can touch type and one who has to hunt and peck, the difference between them is not just down to typing speed. The hunter-and-pecker has to think about typing! This consumes attention and short-term memory that is sorely needed for thinking about the program itself.
I never learned to touch-type, but I've also typed a lot of stuff[0]. I seem to be a lot faster than most folks, and I write wordy code. Take a look at my codebases, to see what I mean. Lots of documentation[1].
Also, I have a friend who is an amazing programmer, but has been absolutely clobbered by RSI. It looks like the worst case I've seen. He's had at least one operation. Maybe two, by now. I think they didn't fix the issue, just ameliorated it a bit. It really does break my heart, because I consider him to be a treasure to programming.
I like my code to be performant, and I seem to be able to get releases out the door in good time, but I suspect the author would go crazy, looking at me work.
[0] https://stackoverflow.com/story/chrismarshall https://stackoverflow.com/story/chrismarshall
[1] https://littlegreenviper.com/miscellany/leaving-a-legacy/ https://littlegreenviper.com/miscellany/leaving-a-legacy/
- godDLL 5y agoCan you finish a thought tho? As in, why did you just type all that up? What is the point you're making? Respectfully.
- ChrisMarshallNY 5y ago> Can you finish a thought tho? Yes ... No ... Maybe ... Tell ya what ... lemme get back to you on that. I gotta ask my wife... > As in, why did you just type all that up? What is the point you're making? Huh? It pretty much speaks directly to to the OP. I’ll pretend that this wasn’t a rather strange troll, and answer the ... um ... ”question.” I'll try to use vernacular, so it's clear. The author talked about how they have a process that they use to speed up the “raw” mechanics of software development. They specifically wrote that they believe that a “touch-typer” is a more effective programmer than an untrained “hunt-and-pecker.” I wrote that I am a “hunt-and-pecker,” and that I believe that I am quite effective. Since this is HN, I backed up my statement by pointing to proof (the canon of my work, as catalogued in my SO story), and, as extra credit, I also pointed to an article that I wrote, discussing how I document my code. I've been writing since I was a wee bairn. I've written a 400-page book (which was never published, because it was embarrassingly out of date, by the time the editing was complete), and, if you follow that link I provided, you'll see a lot of writing. You may be bothered by my longform posts on HN, but these are TL;DR, compared to my normal prolix prose. I also mentioned a personal anecdote, about a good friend, who is a trained touch-typist, and an excellent software engineer (and about a quarter-century younger, but I didn’t feel the need to mention that). His touch-typing directly led to a serious case of RSI (Repetitive Stress Injury), that required two operations (UPDATE: He hasn’t received his second one yet). This RSI was bad enough to negatively affect an extremely lucrative career. Speed can be a curse, as well as a blessing. > Respectfully Sure, whatevs.
- godDLL 5y agoThanks, that cleared that up.