Programming involves long periods of thinking interrupted by short periods of typing. Anything you can do to reduce the mental effort of typing reduces the impact of this interruption to your train of thought.
Try programming by hunt-and-peck typing -- it's certainly possible, but having to think about putting each individual character on the screen is incredibly tedious and distracting. This is why people learn things like Vim motions or minimalist keyboard layouts -- anything that speeds up the feedback loop between your brain and your code is an improvement. It's not a drastic difference, but it's significant enough that I now feel mildly annoyed using a regular keyboard when I have to move my whole arm to reach the arrow keys rather than having them right under my fingers on the home row.
Also as I am typing one thing I am thinking of another, or even third, so if something goes wrong with the mechanics of the first thing, then whole set of dominoes fall and I have to go back.
Sometimes for a given thought I even type 3rd of 4th word instead of the first if for some reason my keys are not pressed. And then I type a word from the next thought and etc. It even gives me anxiety.
As I am typing the code, I am thinking about the code that is going to use the it, and then the code one layer up, I also think of the machine itself, its wires, cache lines, or I think of how the variable I am typing now is related to its surroundings, I imagine a ladder to the moon each step with its address, and I think how far are things from "me", and so on.
I cant speak of others, but for me keyboard layout and even key feeling/rythm is important just because it allows me to think uninterrupted.
I am very happy that apple moved away from the quest of making the keyboard 0 height.
It's true that it will lead to healthier wrists and more productivity, but thats not the point. I know people with incredibly unergonomic setups and habits (vscode with membrane keyboard and a chronic overuse of the mouse) that get around the same or more actual features implemented as me. There might even be something to be said for more friction forcing you to think more.
The reason most of us do it (at least if we are honest with ourselves) is because it's fun---and that's ok. Jumping around in vim on a split keyboard gives me the same joy that watching my first lines of code execute in Gamemaker Studio 2 did in 8th grade.
It's always worth investing to make your work joyful.
In fact, I wrote all this out using a dictation tool in ~20 seconds (258 WPM).
Built one for myself. It's context-aware and promptable.
Tested well on Linux, not so much on other platforms but in theory should support them.
It's a bit meta but I wrote it mostly using Claude Code. Once I had an MVP, I was able to prompt much faster by just speaking out what I wanted it to change.
I also have a whisper dictation app on my Android phone (the app's ID string is 'org.woheller69.whisper', there's a few Whisper apps with the same name "Whisper", but this one is my favorite).
FWIW this was typed by hand on my phone, but these apps are both amazing.
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.
I actually switched to an alternative layout and minimal keyboard like this just because it’s fun. If I can make my work day more fun, that’s a win in my book.
My "fancy" keyboard is a lot like that. It lets me do some customizations that I really enjoy (ctrl when I hold z and /, esc + win next to a and ', "CAPS WORD", using thumbs for more than just space). I just enjoy using it more. Though it does have a few rough edges I probably need to see if I can fix, I CAN fix them.
I am however thinking that I probably would prefer one of the low-profile ones that is more like a laptop keyboard keys, the regular Cherry Blue desktop keys I feel like I'm tripping over a lot.
Speed is rarely a consideration in the community.
I tried many things over the years including other ergonomics and gym etc.
Changing to a smaller split keyboard helped the most and I have not had pain since.
Granted mine has about 50 keys or so so it's not as extreme.
Most keyboards have not spent a single thought on ergonomics, unlike chairs where it is common. There's not a lot of real research in this area and there are contradicting theories (some physicians even say that creating muscle in certain areas like the neck is not worth in the long term). Microsoft ergonomic keyboards have some studies behind and many people report success on split and column staggered keyboards.
wish more people would heed this advice. my wrists are jsut as good as when I was in my 20's. in my early thirties I was starting to develop issues. they went away as soon as I started deadlifting and pullups regularly.
Yoga, climbing, martial arts, swimming; there's no end of fun activities that lead somewhere while keeping you in physical shape.
i also assume that if you have RSI/carpal tunnel/etc then experimenting with your keyboards switches from negative switching costs to greatly positive