typing.io is much better in my opinion
Typing Practice for Programmers
91–100 of 172 posts
Re: Typing Practice for Programmers
#92This is just silly and misguided.
A great quote from Lambert:
1. Decide what the program should do. 2. Decide how the program should do it. 3. Implement these decisions in code.
Only the last part is actually coding.
In other words, you are not paid for typing fast. You are paid to type as little as possible to solve problems!
Re: Typing Practice for Programmers
#93Earlier quoted context omitted.
That's second to the best typing game ever made, Typer Shark Deluxe. I wish there was a modern sequel so deeply! http://store.steampowered.com/app/3450/ https://www.youtube.com/watch?v=4Hr6drzeFgs
I've been toying with the idea of making a spiritual successor to this for years, always been too busy with work though. It's one of my favourite games of all time! Maybe there's some artists/developers here that would want to collaborate to reduce the time burden a bit? :P
I used to make my babysitter play while I watched, because I was astounded she could do so well on hard. Now I play on X-Treme and see if I can make it to the end.
Re: Typing Practice for Programmers
#94Programming is a unique field: if you're doing it right, it should never be dull. Frustrating? Draining? Rage-inducing? Sometimes. But not mind-numbing. Why? Because we can build our own tools. If we find ourselves doing repetitive work, we can build a tool to automate that work. This automation is itself likely at least somewhat interesting. What isn't repetitive and that can't be automated should be interesting as…
Being able to type quickly and accurately is enjoyable. It lets my brain stay focused on what I'm writing rather than how I'm writing it. No context switches necessary, no mistake every 10th key; typing should be fluid and easy. I highly recommend improving your keyboard skills if you struggle with touch typing.
That said I agree that "Typing Practice for Programmers" on "SpeedCoder.net" is a little silly. Just learn to use a keyboard (and learn to spell, that helps too).
Re: Typing Practice for Programmers
#95Programming is a unique field: if you're doing it right, it should never be dull. Frustrating? Draining? Rage-inducing? Sometimes. But not mind-numbing. Why? Because we can build our own tools. If we find ourselves doing repetitive work, we can build a tool to automate that work. This automation is itself likely at least somewhat interesting. What isn't repetitive and that can't be automated should be interesting as…
I'm awful at typing. My friends make fun of my rapid chicken-pecking.
I shrug and say I don't type enough to mind.
Re: Typing Practice for Programmers
#96I would rather prefer a tool that trains me to use my editor/ide more effectively.
Re: Typing Practice for Programmers
#97Earlier quoted context omitted.
I see where you're coming from, but this tool is still valuable in a number of cases that I don't think you're considering. I recently got a new mechanical keyboard, which had special "layers" for punctuation. "Common" punctuation like periods and commas are still there, but other punctuation like curly braces, brackets, etc. require new key combos. [1] I agree with you that a lot of the time programming requires mod…
I built a Planck, and as much as I appreciate the ortholinear layout, I'm having a hard time finding/configuring a keymap that has the necessary symbols somewhere that feels intuitive. I'll spend a couple hours acclimating to a keymap on typing.io, but if I need to an ANSI staggered KB, even for a couple hours, it seems to wipe my muscle memory. Guess I need to buy another Planck!
Keep practicing. I've used an ergodox for about 4 years with the Norman layout. I am still proficient at qwerty on laptop style keyboards.
Though I'm not a musician I assume it is similar to playing two different instruments.
Re: Typing Practice for Programmers
#98Programming is a unique field: if you're doing it right, it should never be dull. Frustrating? Draining? Rage-inducing? Sometimes. But not mind-numbing. Why? Because we can build our own tools. If we find ourselves doing repetitive work, we can build a tool to automate that work. This automation is itself likely at least somewhat interesting. What isn't repetitive and that can't be automated should be interesting as…
This is why no matter how much sense it makes to use something like vim or emacs as your primary development editor, I could never justify the amount of time it would take me to actually be totally comfortable and start seeing benefits (beyond just using it for small quick edits at the command line). Typing speed is never the bottleneck. You could double most developers' typing speed when they code and it'd probably…
If you don't think vim or emacs is worth it then fine, but you're setting up a strange false equivalency between learning new concepts and learning new tools. The fact is, you can't program without tools, and practice will make you better with the ones you choose. If you only ever learn new patterns and algorithms and just type your code into Notepad then you will be handicapped as a working developer.
Personally I choose vim for the exact reason you choose not to: that is I want the ability to edit files in any language on any system I touch with maximum efficiency. This accelerates my ability to try new languages because I don't need to rely on language-specific tooling. Also, vim has more longevity than many design patterns which are susceptible to obsolescence by new language features, and new languages themselves which have a half-life proportional to their age.
Re: Typing Practice for Programmers
#99At the last character (}), I pressed Enter (as anyone would!) which actually resulted in closing the results window before I could read them!
Re: Typing Practice for Programmers
#100I tried out the Javascript section. I tried typing the first word, `animateToOverview`. But when I get to lowercase "t", it asks me to do the shift. It seems that its broken.