Hacker News Reader

are you under the impression that learning to touch type is somehow going to make you worse at typing better code, or somehow hinder your ability to quickly decide what to type?

what a weird career limiting decision to make.

View on HN

I'm in a weird halfway space when it comes to touch typing - I can't intentionally touch type, but I sometimes catch myself doing it unintentionally out of muscle memory. There is no significant change in my productivity between when I do or don't touch type, because I'm in the same boat as the gentleman above: I'm spending more time thinking about, designing and navigating code to build a mental map of the changes I need to make and its effects than I am doing the actual code changes, and I often find that means I only need to make those changes once.

It’s the opportunity cost. Why would I learn to touch type when I can instead learn something with a greater payoff?

You could, but we're here on a Sunday afternoon arguing about this when you could be learning about something with a greater payoff. If you were optimizing for that, you'd be somewhere else. In the time you took on this thread, you could have learned home row and done a touch typing lesson. Instead, it seems like you've made the decision not to learn it and are now just casting about for justifications why you're right not to. Which is entirely up to you, it doesn't affect me if you do or don't learn it, but at least be honest with yourself that you just don't want to because you're afraid or something instead of pretending that you're off learning about new programming techniques in place of learning to touch type, when you clearly aren't.

Of course not, I don’t devote my whole life to furthering my career, that would be crazy.

Reply on news.ycombinator.com