I wish Plover supported Wayland.. it looks like a lot of work from lots of different people went into different workarounds but nothing that managed to end up in a mergeable state as yet
Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
81–90 of 110 posts
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#82Earlier quoted context omitted.
Somewhat hilariously, having perused your first two links, and followed the link from Sweep to Ferris, I still find myself having no idea how any of this works. (But I know a lot about how the firmware and PCB layout is designed!).
I have a charachorder. It's similar to music theory where you can hit individual notes to make up a chord. With chording you hit multiple keys usually that are part of a larger word and it outputs the associated word. This means instead of having to hit every individual key in sequence to type out a phrase one character at a time, you hit multiple keys at once to output words at a time. In the time it takes to output…
I would imagine that programming languages need another vocabulary and you will also need to deal with LongVariableNames, delimiters, tabs etc.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#83I 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.
There are some days with a combo of slow thoughts and a tough problem that my brain can easily be out paced by paper and a crayon or even a quill pen.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#84I don't think I have the skill to learn a stenographer's keyboard, but I would love to have a small chorded keyboard just for macros. I always liked the look of Doug Engelbart's one in the Mother of All Demos. It's very basic, but I'd be quite satisfied with something like that today. He demonstrates it at about 1:40: https://www.youtube.com/watch?v=B6rKUf9DWRI
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#85Earlier quoted context omitted.
Somewhat hilariously, having perused your first two links, and followed the link from Sweep to Ferris, I still find myself having no idea how any of this works. (But I know a lot about how the firmware and PCB layout is designed!).
I have a charachorder. It's similar to music theory where you can hit individual notes to make up a chord. With chording you hit multiple keys usually that are part of a larger word and it outputs the associated word. This means instead of having to hit every individual key in sequence to type out a phrase one character at a time, you hit multiple keys at once to output words at a time. In the time it takes to output…
I still find it pretty humorous that I can't really find any of that information on how this works on these websites. There must be an intro somewhere that they could link to!
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#86In 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.
Raw typing speed is not a blocker to being a good programmer. However, I've generally found that if someone types fast (and uses shortcuts especially in his editor), it usually a sign that he's done a lot of it and that has proven to be a decent proxy for coding experience. This is specifically for junior developers.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#87Earlier quoted context omitted.
Raw typing speed is not a blocker to being a good programmer. However, I've generally found that if someone types fast (and uses shortcuts especially in his editor), it usually a sign that he's done a lot of it and that has proven to be a decent proxy for coding experience. This is specifically for junior developers.
This is why typing tests were popular during SWE interviews back in the day.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#88Earlier quoted context omitted.
Dvorak is much more comfortable than qwerty, in my opinion. I never actually cared about speed, it just feels better.
Dvorak keyboard's fatal flaw is when you have to type on someone else's keyboard. Standardization has its benefits, even if less than ideal. Trackballs have a similar issue.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#89Earlier quoted context omitted.
Yes, I doubt the people paying you to write code will find that argument very convincing...
...are people actually paid to write code? It's a means not an end!
For instance, when I was freelancing, I would be hired by people to write code for their websites, in Javascript and PHP. Telling my employers that I wrote the ideal amount of code (none) would not be satisfying to them. They would not be willing to pay me for the code I didn't write. Outside of the SV bubble, that kind of thing doesn't fly.
Re: Ask HN: Has anyone tried adapting a court reporter keyboard for writing code?
#90Earlier quoted context omitted.
Dvorak is much more comfortable than qwerty, in my opinion. I never actually cared about speed, it just feels better.
Dvorak keyboard's fatal flaw is when you have to type on someone else's keyboard. Standardization has its benefits, even if less than ideal. Trackballs have a similar issue.
I really don't use other people's computers that often, but mice aren't that hard to use (just uncomfortable) and I can still type in QWERTY at about 25WPM but I'd have to look at the keyboard a bit.
Trackballs and Dvorak are both more comfortable than their alternatives, but the real benefit is the reactions I get when other people try to use MY devices when they're not prepared lol