Do you read code while sitting on your hands? Or do you perhaps print out code before reading it?
When I read code, it's not a passive activity. I'm navigating and searching. Sometimes I bring up external documentation. In short, I'm interacting with my computer. For me, reading code requires typing.
> I'm navigating and searching. Sometimes I bring up external documentation.
If you spend as much time navigating as reading or analysing you have an organization problem.
> In short, I'm interacting with my computer. For me, reading code requires typing.
I can concede that when debugging one must press keys to make the ide progress through code however I find spending $100 to comfortably press a key every few seconds wasteful.
Managers, on the other hand, might benefit of good keyboards if they spend most of their time writing emails back to back.
I wonder if there's ever been a study to determine how much the advent of a second standard computer monitor in (developers / accountants / lawyers) toolkits reduced the amount of paper waste generated by corporations each year.
It depends a lot on where you work I've found. I recently had the chance to experience a team where they were given the full implementation logic by a product team, and your job was to turn it from business logic to code almost 1:1. I spent nearly all my time writing and testing, which was an interesting change.
You're right statistically, but think back to what your most "productive" moments of your developer career involved.
It was probably typing furiously. Maybe not a constant dictation stream 150+WPM, but it was surges of input in response to a creative flow in your mind.
Except for the part that programmers spend far more time reading than writing.
An ajustable monitor and a good chair payoff way more than an expensive keyboard.
I still don't get the keyboard hype.