3 ms·
I'll address your points one by one. First off, programming does not involve that much typing, even technical writing is very doable with normal qwerty at 100wp
by rjh29 5y ago
I'll address your points one by one. First off, programming does not involve that much typing, even technical writing is very doable with normal qwerty at 100wpm or so. You only see people using chorded keyboards in fields that involve typing with very little thinking, such as court stenographers. Typing is not the bottleneck for most of us.
As for discussing and buying exotic stuff - that is a vocal minority of engineers. You do not need a fancy mechanical keyboard or 10 years of VIM experience to do your job. Very few people 3D print their own keyboards!
Finally, unlike dvorak or colemak (which are pretty rarely adopted in themselves), tiling window managers or any other form of 'opinionated optimisation' - these things require hardware. They're in the same category as vertical mice. No matter how much better they are, it's going to take a lot more effort to a) buy the hardware and b) insist on having the hardware with you everywhere you go. For most people in most configurations, that bar is too high.
I didn't see you mention RSI or other wrist problems. The one way chorded keyboards might become popular is if we have a large number of engineers end up with severe wrist problems in the course of their normal job. Then you'd definitely see a surge in interest for alternate typing methods. But so far it seems only a minority of engineers end up with these problems.
- closeparen 5y agoI work in Go. The speed at which I can get text into an editor is absolutely a factor in productivity, particularly for meeting unit test coverage requirements. However it is formulaic enough that copy/paste and editor snippets/macros do the job.
- avl999 5y agoHow fast you can get code into an editor is never a bottleneck or a drag on productivity. Kubernetes is the biggest go codebase that I know of and is 1.04 million lines of Go code (even included all automatically generated code). Conservatively assuming each line is 20 words (it is likely way way lower but lets use that as an upper bound) and you are typing everything with no copy/paste or autocomplete allowed and you are typing at 50 words per minute- a team of 10 developers could write all of Kubernetes Go codebase in a little over 3 months of writing code for 4 hrs a day 5 days a week if getting code into the editor was the only or even a major impact on productivity.
- AtlasBarfed 5y ago... This is a hilarious counterpoint.