I don't understand why I need to sign in to try this out. Glad you're getting rave reviews in this thread but I'm passing on the basis that I believ this sign in is unnecessary and creates yet more data exhaust.
Typing Practice for Programmers
141–150 of 224 posts
Re: Typing Practice for Programmers
#142I don't understand why I need to sign in to try this out. Glad you're getting rave reviews in this thread but I'm passing on the basis that I believ this sign in is unnecessary and creates yet more data exhaust.
[deleted]
Re: Typing Practice for Programmers
#143This is the best project I've encountered at Hacker News so far. Thank you.
Re: Typing Practice for Programmers
#144Earlier quoted context omitted.
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.
I agree. I believe the most typing classes are focused on the word processing end of things rather than programming. While waiting to correct errors afterwards can be faster for regular documents, I would absolutely never do that when programming.
Re: Typing Practice for Programmers
#145Earlier quoted context omitted.
I can't really imagine that working very well when coding. It'd cause huge issues with autocomplete and autoindent.
I agree. I believe the most typing classes are focused on the word processing end of things rather than programming. While waiting to correct errors afterwards can be faster for regular documents, I would absolutely never do that when programming.
Actually, I doubt it's even better for regular documents.
In the writing discipline, people will often tell you to write a first draft without correcting errors, then go back and error-correct on the second draft. But that's not about typing errors, but rather grammatic/narrative errors in your writing.
Re: Typing Practice for Programmers
#146It 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).
yea, german keyboard here and it doesn't recognize my "=" ( so couldn't get past line one. Looks really cool though, I hope it gets I18lized sometime soon :) KeyboardJS has a basic locales mapping: https://github.com/RobertWHurst/KeyboardJS , Unfortunately it appears to only have en_US at the momment though
Japanese keyboard user here.. I'm sure that ( is above the 8 :)
Re: Typing Practice for Programmers
#147Does not support other keyboard layouts than US I think. Good idea though.
Re: Typing Practice for Programmers
#148It seems like It is interesting. I wonder if I can learn to make fewer typos.
I also had problems with the fist line in the rails example:
require 'active_support/core_ext/object/blank'
I have a swiss german keyboard and I can't get past the first _'_ character. I'm using XP and Firefox. Otherwise a really neat idea.
Re: Typing Practice for Programmers
#149Does not support other keyboard layouts than US I think. Good idea though.
yes, my demo stops at (
Re: Typing Practice for Programmers
#150This made me aware that i typed ":" with my RING FINGER. wow. What have I been doing...