Nice. Writing code is very different. People mostly seem to train English word-lists to increase wpm. But for code you constantly have to deal with new words, prefixes and special characters. Awkwardly placed special characters on the keyboard can ruin the flow. Dvorak, Colemak don't have any improvements over Qwerty - so they're most likely pretty useless.

Layouts with nicely placed special characters are all very non-standard. Building a custom keyboard nowadays is quite easy, but it takes some courage to train something that is seriously less standard than Dvorak ever was.

I think the problem with this approach is that when I type, I don't type formatting because prettier can do that for me.

By far the biggest two things screwing me up here are problems with the app itself: The single-quote opens up the browser's quick-search, leaving the app and screwing up the flow, and the automatic yellow text that moves at a constant speed is extremely distracting if it ever gets ahead of me because of how much more visible it is compared to where the cursor actually is. And it's almost guaranteed to happen on the ones that use single quotes because of the first problem.

Use practice mode so you don't have the competing cursor!

Will look into the singlequotes issue!

I like it but it's not really a comparable/usable result. My IDE auto suggests a lot of things and a lot of "words" could be reduced to a single tab key press.

For example, in golang, I have not typed a full if err != nil {} in years. "err.nn"+tab auto completes to the if, and "err.re" auto completes to the if + return err. To be able to compare what speed I really code at, I should be able to use these to speed things up.

Same as calling functions, I rarely type the full name and instead use tab auto complete. Same for for ranges, "nums.forr" autocompletes to the for i,n := range nums {} form.

Yes, but at the same time in a technical interview you don't control the IDE and you need to type it out. I.e. google interviews on a google doc.