Typing Practice for Programmers
71–80 of 224 posts
Re: Typing Practice for Programmers
#72Re: Typing Practice for Programmers
#73Other 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
#74Re: Typing Practice for Programmers
#75Re: Typing Practice for Programmers
#76It 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
#77This 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
#78Regarding 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
#79Please find some code that isn't laden heavy with use statements. I'd expect my editor to autocomplete these...
Re: Typing Practice for Programmers
#80Earlier 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.