3 ms·
There has been some effort to make a keyboard layout better for programming, namely Programmer Dvorak. It's certainly not amazing by any means, as the reorderin
by snuxoll 10y ago
There has been some effort to make a keyboard layout better for programming, namely Programmer Dvorak. It's certainly not amazing by any means, as the reordering of the numerical keys really stinks, which is why I stick with the traditional dvorak layout (which actually has some disadvantages in curly-brace languages since the {} keys are right next to backspace and require moving my entire right hand off the home row to reach comfortably, whereas the traditional QWERTY locations can easily be hit by my little finger).
As much as neat devices like the data hand and other input devices make waves on HN every now and then, I feel most programmers are just like the rest of the world, they just use QWERTY because that's what they learned and never saw anything wrong with it.
- consto 10y agoI would be surprised if switching to a slightly nicer keyboard layout would overcome the loss of muscle memory.
- snuxoll 10y agoIt certainly takes time. I never learned how to touch-type on QWERTY (I got really fast at pecking at keys) - so taking the dive from ~30WPM to ~15WPM for the first two weeks wasn't too big of an issue, now if most of the online typing tests can be considered "good enough" I now type roughly between 80-95WPM on average using Dvorak - which is mostly excessive when it comes to my day job of programming since I spend more time thinking about what I'm trying to write than I do typing it, but it comes in handy when replying to comments on Hacker News and Reddit or when I have to type up documentation.