4 ms·
How to type on a keyboard. I don't think you have to have perfect touch typing, but you should be 30 words per minute at the very least. The other one is test
by lsiebert 14y ago
How to type on a keyboard. I don't think you have to have perfect touch typing, but you should be 30 words per minute at the very least.
The other one is testing and debugging. Something I'm always trying to do better, personally, but whatever you do, understanding both the process of debugging, but also the though process (edge cases, common issues, breaking problems up into sub problems, etc.) is important.
It's hard to talk about generic skills for computing though. There are many useful skills I have, but I'm not sure they cross domains.
- CrLf 14y agoFunny enough, in every discussion that I have about this subject typing never comes up... Indeed there are a lot of people in this profession than can't type properly. I wonder if this isn't one of the underlying issues when discussing CLIs vs GUIs.
- tqc 14y agoTyping isn't nearly as important as it may at first seem - how much code do you really type? Sometimes I might produce 10 lines of code in a day, all the effort going into knowing exactly what those 10 lines should be. Even the worst typist can beat 0.05wpm.
- CrLf 14y agoTyping isn't just coding. Even if you code a lot, you probably spend more time typing other things than code. The importance of typing fast is not letting your typing slow you down.
- tqc 14y agoThe same applies there, albeit to a lesser extent - if typing slows you down, you might not have thought things through. That said, I have been typing more than writing for many years and am now thoroughly incompetent with a pen.
- lsiebert 14y agoActually I spend a lot of time typing documenting my code, so that my though process at the time is clear.