[irjustin]

Why bring the whole Devorak part into the article? Also, I'm surprised the author didn't go pure stenograph then because that's way faster.

WPM is only a good measure of WPM.

The best coders don't need to type faster. The best writers still hand write things or type on DOS[0]. Once you hit a baseline competency, other areas of improvement/reward far outweigh the time devoted than to a better WPM.

Wanting to type faster is fine, but do not mix it with being more effective aside from being a great typist.

[0] https://www.youtube.com/watch?v=X5REM-3nWHg&feature=emb_titl...

[emerged]

If efficiency is the goal, it's better to spend time optimizing your ability to use advanced text editing features. Simultaneously modifying multiple lines at once, block based editing / copy+pasting, regexes, etc. I'd imagine the amount of time I'm actually typing is well under 1% of my time as an engineer.

[quickthrower2]

There is a point around 200wpm (?) that I think would be very handy to be able to "type" this fast, using shorthand or whatever. This where you can keep up taking notes when talking to someone but also take in the subject matter. Being able to do that all at once and then have those notes to refer to would be very useful.

A lot of time is wasted by not having a record of things.

Maybe "AI" would be just as good as solving this problem though.

[irjustin]

That's stenography. If you truly need to type fast, there's better tools for the job.