He uses the wrong test. Testing on "The Adventures of Sherlock Holmes" is meaningless for developpers: tests should be performed using real usages like "source code of linux kernel" or "mailing list of linux kernel" to have a better balance between code and text.
Sit up straight (fix your posture) and stop gluing your wrists to the desk or wrist “support” and the layout doesn’t matter unless you’re going for typing records.<p>There is no magical layout that can eliminate the tension you’re artificially creating by stretching your fingers into unnatural positions instead of just moving the entire hand.<p>What healthy typing looks like (on a horrible keyboard no less): <a href="https://www.youtube.com/watch?v=Vs2B5XRtr6k" rel="nofollow">https://www.youtube.com/watch?v=Vs2B5XRtr6k</a><p>Imagine you tried playing a piano the way you type on your keyboard: <a href="https://www.youtube.com/watch?v=InqmH-o1cX0" rel="nofollow">https://www.youtube.com/watch?v=InqmH-o1cX0</a><p>The pain is letting you know you’re doing something wrong.
As a full time developer who used to suffer terrible RSI pain, I solved the problem without changing keyboard layouts. After consulting with my doctor and an ergonomics expert, I realized my problems were cause by the setup of my workstation and the bad posture habits I had developed.<p>1. I would rest my palms as I typed. This turned out to be a major source of pain. Retraining myself to "float" my hands over the keyboard was a massive improvement.<p>2. My desk was too high / my chair was too low. Setting up my desk so that my keyboard is as close to my lap as possible was the next big improvement. When in a seated position, my hands are very comfortable when resting on my thighs. Putting my keyboard in a drawer that is just above my thighs helped a lot.<p>3. I also switched to a trackpad instead of a mount and a split keyboard. I found this allowed a more comfortable angle for my hands and less temptation to rest my wrist while mousing.<p>After making these changes, I have been pain free for over 10 years.
This looks interesting but the symbol still look very qwerty-ish. I type on Neo-2 (<a href="https://en.wikipedia.org/wiki/Keyboard_layout#Neo" rel="nofollow">https://en.wikipedia.org/wiki/Keyboard_layout#Neo</a>), which uses ISO keyboards and primarily targets German, even though the majority of my typing is in English. Its entire third layer is for symbols that are common in programming. Layer 3 is activated via either caps-lock or the key above Right Shift, and has \/{}* ?()-:@ as the home row, …_[]^ !<>=& above it and #$|~` +%"'; below it (there's a picture in the Wikipedia article linked above).<p>Layer 4 (right alt or the key to the right of left shift) is also pretty cool, it has lots of navigation keys and a numblock in convenient positions, but I somehow never got around to learning that. All the layers are shown on <a href="https://neo-layout.org/" rel="nofollow">https://neo-layout.org/</a> (in German, but that doesn't matter for the pictures).<p>With a Trackpoint (Thinkpad USB keyboard), this means that my hands don't have to leave the home row at all. It's super convenient.
> Try typing “The” with the T capitalized on Colemak and hopefully you’ll see what I mean. Your right hand will move somewhat like this: you swing to the right to get the SHIFT key with your pinky, then you swing back to the left to get the letter ‘H’, and then you move to the right again to get the letter ‘E’.<p>Why would you use the right shift here?? I shift with the <i>left</i> pinky in this situation and it feels fine.<p>Colemak is just fine, and it's already included in most operating systems.
If you are looking at alternative keyboards, I have been using the TypeMatrix 2030[0] with a transparent cover for about 10 years.<p>I am using the Dvorak layout, but I think that the main reason it is so comfortable to use is the ortho-linear layout of the keys and that it is totally flat.<p>I would recommend anybody with RSI to test first ortho-linear physical layout of the keys with your standard Qwerty or Azerty or whatever you use right now before moving to something else.<p>[0]: <a href="http://www.typematrix.com/" rel="nofollow">http://www.typematrix.com/</a>
Kudos for effort. But changing layout is not enough.<p>Current mainstream keyboards design is fundamentally flawed [1] and IMO obsolete because of [4].<p>Hopefully there is science [2] and much alternatives to choose from [3]<p>[1] <a href="http://xahlee.info/kbd/keyboard_problems.html" rel="nofollow">http://xahlee.info/kbd/keyboard_problems.html</a><p>[2] <a href="http://xahlee.info/kbd/ergonomic_keyboard_science.html" rel="nofollow">http://xahlee.info/kbd/ergonomic_keyboard_science.html</a><p>[3] <a href="https://github.com/diimdeep/awesome-split-keyboards" rel="nofollow">https://github.com/diimdeep/awesome-split-keyboards</a><p>[4] <a href="https://en.wikipedia.org/wiki/Path_dependence" rel="nofollow">https://en.wikipedia.org/wiki/Path_dependence</a>
> I didn’t like the way Dvorak was laid out especially for the weak fingers of the right hand.<p>I am not sure if I only know this from playing piano and guitar, but it is surprisingly easy to strengthen those fingers. The exercise is very simple and all it takes is a couple minutes a day, it can be done anywhere (even better if you have a piano or guitar!):<p>1. Lay your fingers on a table, and curl them like you were at a keyboard or holding a small ball in your hand.<p>2. Keeping all of your other fingers on the table, lift your weaker finger, typically the ring as high as you possibly can without causing the other fingers to rise.<p>3. Bring it down as hard as you comfortably can.<p>4. Repeat 1-3 until you can lift higher and bring it down harder without affecting the other fingers.
I don't have any RSI issues but I love the idea of alternative/improved keyboards and layouts and have accidentally become kind of an aficionado/collector. I have on permanent rotation and have written reviews of a Kinesis Ergo [0], Truly Ergonomic (TEK) [1], TypeMatrix [2], and Happy Hacker [3] and I'm looking seriously at buying an Ergodox one of these days. I happen to like and dislike each of those keyboards: each has advantages and disadvantages. Same goes for Dvorak (which I use regularly) and Colemak, etc. I'm hard pressed to say which is my favorite, but I like each for different reasons and conclude it would be impossible to combine them into any "perfect," ultimate keyboard.<p>One thing that almost never comes up in these discussions is the need to change or rotate keyboards. I love the Kinesis but eventually get tired of it, and am happy to move to the TEK, which then starts to bother me until I move to the TypeMatrix, etc. Every keyboard and layout improves some part of typing while exacerbating another. Switching keeps you nimble. I suspect it's like bicycles, of which there are infinite variations. If one bike hurts your wrists and another hurts your legs and another bothers your neck, switch every few rides.<p>[0] <a href="http://therandymon.com/index.php?/archives/167-Typing-in-Style-with-the-Kinesis.html" rel="nofollow">http://therandymon.com/index.php?/archives/167-Typing-in-Sty...</a>
[1] <a href="http://therandymon.com/index.php?/archives/290-The-Truly-Ergonomic-Keyboard-TEK-Review.html" rel="nofollow">http://therandymon.com/index.php?/archives/290-The-Truly-Erg...</a>
[2] <a href="http://therandymon.com/index.php?/archives/295-The-TypeMatrix-2030-Ergonomic-Keyboard.html" rel="nofollow">http://therandymon.com/index.php?/archives/295-The-TypeMatri...</a>
[3] <a href="http://therandymon.com/index.php?/archives/304-Review-of-the-Happy-Hacker-2-Keyboard.html" rel="nofollow">http://therandymon.com/index.php?/archives/304-Review-of-the...</a>
A keyboard layout for programmers, which allowed the use of special characters on the home row, perhaps by using a mixed corpus of source code rather than just novels, would be interesting to see.<p>Recently, I ordered the Ultimate Hacker’s Keyboard because I think typing is quite important for a programmer, especially if you consider health as the author of this article does. I’m a little bit weary of <i>not</i> using QWERTY because of the high cost of switching, so if I did switch, I’d want to select a layout that was basically perfect for me long-term (which sounds very tough to do).
I left Colemak for Qwerty some 5 years ago. Keyboard layout matters much less than your typing technique.<p>Same thing for ergonomic keyboards - they can be a dangerous sign that you're focusing on the wrong thing, on micro-optimizations rather than on the root cause.<p>I have no guide to share unfortunately but I'd recommend observing one's movements, and try to figure out what's the most natural way of doing a given thing.<p>Also, regardless of what you do, typing many hours will tire you / be painful. Act accordingly.
I have been using this for ~4 years. So far I like it, it is extremely comfortable to type on and instantly felt better than eg. colemak to me, though I never learned to touch type as quickly on any other layout. However, I wish I had just stuck to qwerty in the end, as I use vim keybindings wherever possible and the extra steps needed to customise the keybinds in each application is a hassle, and sometimes not even possible.
Anything other than [AQ]WERT[YZ] layout-based keyboard is already a big improvement for your fingers. The differences between Workman / Colemak / Dvorak and so on is mostly a matter of taste. One thing to note is that widely used layouts have more chances to be supported by software and by keyboard manufacturers (e.g. <a href="http://www.typematrix.com/" rel="nofollow">http://www.typematrix.com/</a>). So it may be wiser to choose mainstream layouts that creating your own or using niche ones.<p>There is probably not a definitive answer for which one is better ("better" would have to be defined for this), so go ahead, read a bit about them and do your choice. Be aware though that once you have choose one, you will be stuck with it for a looong time, because switching layout is <i>hard</i>. You have to remap all your brain an muscle memory before being able to reach your previous efficiency. Spoiler alert: it takes months to years for this.<p>PS: For french speaking people, you may want to have a look at <a href="https://bepo.fr" rel="nofollow">https://bepo.fr</a>
The author doesn't even learn dvorak before deciding that it doesn't work for them. They mention don't like how it behaves on the consonant-heavy, qwerty-optimized commands used in unix. (I have to say this is a fair evaluation, but in practice the layout somehow doesn't encourage RSI despite the apparent awkwardness of typing unix commands on it.)<p>In result they don't seem to understand that the dvorak layout is optimized for alternation between hands (they do mention this) <i>and</i> inward rolling motion (they don't seem to understand this). You can really feel this when typing, and it makes typing downright enjoyable.<p>I wouldn't be surprised if much of the added distance relative to colemak and workman is probably reaching for the "i" with the left pointer finger. These are the easiest movements to make repeatedly, and in my experience the home row horizontal movement that they try to optimize out of workman isn't really important.<p>People should be free and encouraged to make their own layouts to beat RSI. But, scientific measurement of what is better seems basically impossible...
check out QMK keyboard firmware at <a href="https://github.com/qmk/qmk_firmware" rel="nofollow">https://github.com/qmk/qmk_firmware</a><p>do whatever you want with layouts, macros and layers without any need for software or driver on the host machine
My biggest issue with traditional keyboards is using non-alpha keys like the arrow keys, modifier keys, punctuation, numbers, escape, and function keys.
I (sorta) solved this issue by getting an Ergodox and designing a qwerty layout[1] that made the modifier keys thumb accessible and other non-alpha keys close to the home row through layers:<p>- navigation layer: arrow keys and tab navigation on the home row.<p>- number and symbol layer: numbers on the home row, function keys one row above and punctuation one row below.<p>Its still a work in progress but I think it has helped me.<p>[1] <a href="https://configure.ergodox-ez.com/keyboard_layouts/zjdlgd/edit" rel="nofollow">https://configure.ergodox-ez.com/keyboard_layouts/zjdlgd/edi...</a>
I feel Carpalx has a less arbitrary, more rigorous solution to this [1]. I've been using its QFMLWY for years. It is hugely better than QWERTY. Though as a programmer, I'm still not fully happy with the Ctrl and Shift keys being in their standard location, and thus at the weakest (pinky) finger.<p>If anyone would like to give QFMLWY a go, let me know. I have scripts to install it on Win, Mac and Ubuntu.<p>[1] <a href="http://mkweb.bcgsc.ca/carpalx/?full_optimization" rel="nofollow">http://mkweb.bcgsc.ca/carpalx/?full_optimization</a>
It is interesting, given that the corpuses are available, that keyboard design isn't framed as some sort of linear or nonlinear optimising problem.<p>Choose a set of tasks -> plug into an optimiser -> get a keyboard mapping tuned to the task you are doing. There'd be people who find that useful. The maths isn't at all hard, the data is there.<p><i>EDIT</i> Maybe it would be a fun project to take something like top 100 C libraries from github and build up an optimised keyboard layout for C coding. It is an interesting idea.
The Colemak Mod-DH family of layouts incorporates the major insight of Workman (that QWERTY v and n are lower-effort positions than QWERTY g and h) without abandoning the better elements of Colemak (common left hand shortcut keys QWAZXC remain unmoved, good hand alternation, emphasis on inward rolls).<p><a href="http://colemakmods.github.io/mod-dh/" rel="nofollow">http://colemakmods.github.io/mod-dh/</a>
My thoughts:<p>- if the author of the article is moving his fingers laterally, probably he is doing something wrong (must use other fingers instead of moving, this is typewriting). Independent of the layout, this cannot happen.<p>- I believe that there is no silver bullet for keyboard layout if you write code and text, more than one language, statistics of your typing are unique for the languages you currently use.
I'm glad that alternative keyboard layouts seem to be gaining traction but I just can't go cold turkey and move away from QWERTY.<p>The biggest annoyances for me with regular keyboards are that caps lock is a wasted key in a prime position and the F keys are too far out of the way.<p>These were solved by the HHKB and that's what I'll be using for the foreseeable future.
A large portion of coding is moving the cursor left, right, up, down, page up, page down, home, end<p>The arrow keys are not even shown on the layout.<p>And the selection of prose corpus (es?) is again not related to programming [Tom Sawyer].<p>We need underscores, braces, semicolon, context menu.<p>Perhaps a better metric would be the hoc compiler source from The Unix Programming Environment.
I moved to Dvorak year ago. Very very happy with this.<p>The pain of my hands, especially on the weakest fingers, just ended. The sad is that there are no available keyboards to buy in my country, so I always need to manually change and 'fix' my new laptops, risking to break it, and I always do it very worried and careful.
One neat trick (for programmers) is to switch your number row to use the symbols normally and shift to get the digits.<p>As a programmer you type those symbols way more often than digits. It's easy to get used to and it can make a difference if you have RSI issues.
This is an excellent solution to a problem no programmer has. After 10 years of programming I can safely tell that, if you type the majority of your time until you make your wrists sick, you are writing shit code and you should spend more time thinking.
I always type faster with one hand,<p>It is common for me to type thnak you for exemple
Should I be using an layout with low hand switching?
Dvorak?
Thanks
I always type faster with one hand,<p>It is common for me to type thnak you for exemple...<p>I guess i should look at a layout with little hand alternance,
Dvorak?<p>Thanks
I love how inclusive this comment is "a difference of 696 meters. It doesn’t sound like much, however if we convert it to centimeters, that’s equal to 69,600 cm" :D