typing

If you mean run RPython code as regular Python code, that doesn't always catch typing problems.

Actually Vista added one of my most-used time-saving features: Windows-key and start typing to search.

Experienced manual typists learned not just touch-typing but the correct rhythm to minimize the time between keystrokes without quite jamming the machine.

One could relatively easily judge if you were pushing the mechanism too hard (and adjust accordingly), how evenly you were typing, etc.

Adjacent hammers can block each other without jamming when typing too fast.

I seem to just instinctively copy the syntax of the code around where I'm typing.

You know, I was thinking about that as I was typing my original comment.

But then again, typing usually is not the bottleneck.

I started to learn typing as a kid on an old manual typewriter (didnt have the patience to fully learn but that's not relevant).

Now when my kids are wanting to install more advanced things they are naturally exploring package management and typing into the terminal to get a new thing going.

Turns out she thought that ':wq' was how you saved in vi, and was happy when I told her to try typing just ':w' instead.

Only quoting final sentence since I'm typing this on a phone...

One of my college friends suprised me by "saving" a paper she was working on in vi by typing ':wq' and then typing 'vi <paper>' at the command line.

While i was still very productive, far more than usual, i would often stop typing for moments and go "Man..

Instead of typing "Can someone help me with a bug about Hacker News?" just go ahead and type about the bug!

Way easier than counting the number of lines to delete then typing "4dd" imo.

Typing this from a cheap Acer Aspire V5-471G (the cheapest make and model for given specs).