Depends on your goal. Chording technique is superior when typing words contained in the dictionary. Meaning that typing some rarely used word required typing it multiple times to "confirm". Writing code does not suite well for this, since coding with completion contains much more punctuation than plain text. Instead, check out ergonomic mechanical keyboards: low-profile, split, with columnar stagger, preferrably with…
Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
31–40 of 110 posts
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#32It’s awesome just how fast and accurate they can be, and most devs were of my mindset “wow can I learn to type like that - it woukd solve this problem and that”
Till we found out just how much work is needed to get good. It’s a true skill, and sadly undervalued but something that just has too little pro for the cons - in my opinion as a developer.
I already type at faster than I can code, and slightly slower than I can write English. A better keyboard, or the same keyboard at different workstations and laptops, or some typing tutorials woukd help me - but full on 100wpm is not going to help me debug Kerberos failures
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#33Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#34I can already type on a QWERTY keyboard way faster than I can think. That's one reason I haven't adopted a Dvorak habit. Most court reporters use software nowadays that renders their special stenotype skills obsolete.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#35Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#36Depends on your goal. Chording technique is superior when typing words contained in the dictionary. Meaning that typing some rarely used word required typing it multiple times to "confirm". Writing code does not suite well for this, since coding with completion contains much more punctuation than plain text. Instead, check out ergonomic mechanical keyboards: low-profile, split, with columnar stagger, preferrably with…
Non-qwerty seems to me to be one of the biggest wastes of time we’ve come up with in search of productivity. The time spent learning it could be spent learning vi, learning Haskell, learning to shoot hoops or learning the guitar. Pretty much all of those would benefit you more.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#37Not me. I gave it a trial , but couldn't do justice to it. The key jurors got bored of the case . So I couldn't write a sentence .
Downvoted for a good pun! The HNHEF (HN Humor Eradication Force), like the oft-mentioned-on-HN RESF (Rust Evangelism Strike Force), strikes again! Foo(l)ray!
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#38Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#39In my experience, typing speed is never the issue. I've worked with truly 10x and better programmers in my life and the road block for even them is thinking not typing.
I agree w/ others in this thread about the underlying challenges for using a steno keyboard for coding. You basically need to pick a custom chord for every program identifier, keyword or symbol, and somehow make those chords memorable. Perhaps a custom IDE featureset can help, leveraging the LSP or tree-sitter parsers?
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#40In my experience, typing speed is never the issue. I've worked with truly 10x and better programmers in my life and the road block for even them is thinking not typing.
Thinking is a lot easier when your output is seamless and reliable though. Nothing sucks more than debugging typos. The code should work, but it doesn’t. You know you did everything right, but it just won’t work.
20min later … oh wait it’s a typo. Fix was perfect just mangled between brain and keyboard.
Double bad when for whatever reason you can only debug on a remote environment and every iteration takes several minutes.
Learn to type fast and reliably. It’s easily one of the highest ROI things I ever did.