On Thu, 2007-10-18 at 19:29 -0700, Tracy R Reed wrote: > Paul G. Allen wrote: > > I never learned to type properly. I type with two fingers on each hand > > Is it too late to learn?
Yes. I'm too damned lazy. ;) Seriously though, I've thought about it, but I've always got something else to do. > > Which editor do you use and how does your lack of home row usage affect > your editor preference? I guess hjkl cursor movement doesn't buy you > anything? The editor depends upon what I'm doing, where I'm at (remote console or local, command line or GUI). I don't like hjkl simply because I've become accustomed to using the arrow keys. When I'm at a console where I must use hjkl, I have to think about it first before I can start using them. > > > I guess the bottom line is that as long as the person can get the job > > done fast enough, what's the difference how it's accomplished? > > Most companies consider time to be money. If you are going to require > twice as much time as the guy who knows how to type isn't that a > disincentive to hire you? Fortunately coding tends to involve more time > spent thinking than typing so the difference is not as pronounced as if > you were a secretary. > Which is why I often wish I could type faster. I can think through the problem and figure out how to code it, and then when it comes time to type it all in, I'm not fast enough to make myself happy. Then again, my ideal would be using something like IBM's Voice Type (which I had back in my OS/2 days) so that I could just speak the code, instead of type it. So, this brings us back to: give the candidate a task to accomplish and see how long it takes them. Maybe something like writing a script to do something, which would involve thinking through the problem, solving it, and them typing out the solution. PGA -- Paul G. Allen BSIT/SE Owner/Sr. Engineer Random Logic Consulting www.randomlogic.com -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
