Live data from Hacker News

Typing Practice for Programmers

typing.io

161–170 of 224 posts

Re: Typing Practice for Programmers

#162

It doesn't appear to respect my keyboard layout - I'm using colemak (which works fine) but with UK symbols instead of US (which works everywhere else, including the HN comment box, but not in Typing.io where it wants me to type US symblos: eg " and @ are swapped).

At least they're just swapped. I don't know where it thinks " is on my keyboard :(

Re: Typing Practice for Programmers

#163
post #35

It seems like It is interesting. I wonder if I can learn to make fewer typos.

I had issues with the '-' character (for example, in the first line of the Shell Git lesson), and I'm just using the standard US keyboard layout. EDIT: also '_', as sp332 commented. Firefox on OS X.

Me too with '-', also with Firefox (Nightly) on OS X (10.6.8). However, it seems to work fine with Safari.

Re: Typing Practice for Programmers

#165
post #4

Fun idea, but doesn't seem to recognize non-US keyboard layouts.

Thanks for the bug report. The next update will fix international keyboard layouts once I figure out the mess that is cross-browser, cross-language javascript key event handling:)

Wouldn't it be better to have an input field and simply read what has been typed in it? It's not as if you need to have something else focused while doing it. That would eliminate all international keyboard problems in one go, even without a dedicated library.

Re: Typing Practice for Programmers

#169
post #41

i really like it, but one thing disturbed me. why do you skip the comments?

Good question! I wanted to focus on helping users practice typing code with its often cumbersome symbols. The majority of comments are prose, comfortably near the home row, which I didn't feel deserved as much attention. Plus some comments (like the ones in the Guava projects) are longer than the code.

yeah, but you do not practice comment characters :D.

but valid point nevertheless.

Re: Typing Practice for Programmers

#170
post #101

Earlier quoted context omitted.

Thanks, I'm glad you found the stats useful. In my initial version, I wasn't requiring the user to correct errors. I was personally getting errors rates around 3~5% , which appear good but seemed too low for the amount of errors I feel I make. Adding the need to backspace and correct keys revealed the true cost of mistyping a key, namely the wasted keys typed before correcting and all the backspaces. Thanks for point…

Supporting KILL and especially WERASE would be nice; I usually use one of those rather when I've made a string of errors, rather than watching and counting backspaces. And I agree with previous comments that it's hard to follow just how many backspaces are needed.

that opens a whole can of worms.

i use vim: so please support all vim movements. and the surround plugin. and while at it: my custom templating plugin as well :D.

Post reply on HN