|
There's a lot of ignoring your question and telling an anecdote - some nice anecdotes, though. I'd guess the answer is yes. If someone (somehow) gets into a junior dev role, has no to little experience, and hunts and pecks 20 words a minute, they'll have to get that up to 50/60 surely before they can be a more normally functioning member of a team, right? I think in some bad cases it could be priority number one. If your job is producing text in files, you tend to need basic proficiency in typing. I guess you're rather imagining a really solid developer, types 70/80 wpm but never put any effort in to typing per se, uses whatever system or IDE is the norm and isn't bothered. Learns a few keyboard shortcuts here and there maybe, but again, who cares. Imagine a counter to your question - if that last developer could click their fingers and get to an effortless, consistent 100 wpm, would they? Should they? I think the answer is yes, and yes. They can still spend as much time as they want staring at the ceiling thinking, with the notepad out sketching, etc. Now, not everyone wants to think about it, and that's fine, other things matter more in the end. How pleasant of a colleague you are matters more in many cases. But surely the notion itself of typing faster being preferable is easily understandable - programmers are text file producers. |