Live data from Hacker News

Typing Practice for Programmers

typing.io

71–80 of 224 posts

Re: Typing Practice for Programmers

#71
This reminds me of Learn Code The Hard Way... The guy that runs it states the only way to learn is by typing the code in, bit by bit and not to go too long because you might burn yourself out...This is a nice free tool, Cheers moonboots!

Re: Typing Practice for Programmers

#73
Why can't I share my test results on social networks? This is like one of the only types of social activites / games I would want to share with my friends!

Other than that, this is freaking rad!

I found it funny that I'm normally a 120-150 WPM typist, but when typing special characters for regex, etc, I hit a patch of molasses.

Re: Typing Practice for Programmers

#76
This definitely shows me how much of the coding style I use is in muscle memory, I'm continually trying to add spaces and newlines where they aren't!

It would be interesting to be able to pick specific coding styles for C

I'm spending too long on this, back to work...

Re: Typing Practice for Programmers

#77
post #76

This definitely shows me how much of the coding style I use is in muscle memory, I'm continually trying to add spaces and newlines where they aren't! It would be interesting to be able to pick specific coding styles for C I'm spending too long on this, back to work...

I had this exact same problem! Kept trying to predictively type characters that weren't actually there in the source code.

Re: Typing Practice for Programmers

#78
This is great. You should charge money.

Regarding indentation: I think you made a reasonable choice in excluding it across the board. Definitely better than requiring it to be typed everywhere. That said, ideally you would require the user to make the keystrokes to un-indent whenever an IDE wouldn't automatically.

Also: Something in Objective-C please. Those square brackets took me a lot of practice to get used to.

Re: Typing Practice for Programmers

#80
post #45

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…

I was taught in typing class that its better to skip errors and then come back and correct them when you are done. Not that I follow that advice especially often, but I wonder if it would be more helpful to do that. I didn't like during the demo that I was forced to correct the problem before continuing.

I can't really imagine that working very well when coding. It'd cause huge issues with autocomplete and autoindent.
Post reply on HN