Google Docs vs manual typewriter
tommorris.org
Google Docs vs manual typewriter
1–10 of 27 posts
Re: Google Docs vs manual typewriter
#2Admittedly I couldn't stand to read the whole article. His obsession with typewriters seems to have influenced his taste in font size and family.
My question to others based on what I read is how many people here, without looking, can type quickly and accurately but choose to not follow the homerow practice? I type very quickly, and hardly ever need to press backspace. I usually only look when I type in 16 character passwords with alternating caps.
Re: Google Docs vs manual typewriter
#3Admittedly I couldn't stand to read the whole article. His obsession with typewriters seems to have influenced his taste in font size and family. My question to others based on what I read is how many people here, without looking, can type quickly and accurately but choose to not follow the homerow practice? I type very quickly, and hardly ever need to press backspace. I usually only look when I type in 16 character…
I've never been successful with the home row method, I'll admit; it has always caused severe pain in my wrists. That said, I can type at least 90 wpm without looking at the keys, and that suits me just fine.
Re: Google Docs vs manual typewriter
#4I have respect for the pen, due to its portability, convenience for quick notes and use for making sketches, diagrams, and free-form documents. The type writer, on the other hand is idiotic. It's rigid, even worse than computer documents. It's also completely incapable of handling Chinese, which makes up a large part of what I have to write. On top of that, a typewriter weighs more than a backpack with a laptop inside.
What's next, Mass production vs personal forge?
Re: Google Docs vs manual typewriter
#5Sorry, I had to close the page after reading: "I'm not sure that it's possible to know how to code in as many programming languages as I do"
tldr: It's painfully apparent the author is getting too old to Keep Up and is taking that frustration out on newer technology. Retire already. No one uses gopher or typewriters anymore (for serious work), nor will they ever.
Re: Google Docs vs manual typewriter
#6Admittedly I couldn't stand to read the whole article. His obsession with typewriters seems to have influenced his taste in font size and family. My question to others based on what I read is how many people here, without looking, can type quickly and accurately but choose to not follow the homerow practice? I type very quickly, and hardly ever need to press backspace. I usually only look when I type in 16 character…
On most keyboards it is very hard to touch-type while programming. Seriously, I just can't enter a curly brace while keeping my hands on the home row. It hurts :) And once you move that hand, repositioning it takes time.
The other reason I never learned to type properly is that I just get bored. I tried several times, and always gave up. It just feels like a waste typing fjfjfjfjfjfj when I could be entering code.
Finally, the productivity of a coder isn't how fast he/she can type. It's how well they think, which is mostly inversely related to WPM.
Re: Google Docs vs manual typewriter
#7Sorry, I had to close the page after reading: "I'm not sure that it's possible to know how to code in as many programming languages as I do" tldr: It's painfully apparent the author is getting too old to Keep Up and is taking that frustration out on newer technology. Retire already. No one uses gopher or typewriters anymore (for serious work), nor will they ever.
You should have at least finished the sentence before concluding that it makes no sense. "I'm not sure that it's possible to know how to code in as many programming languages as I do, own an iPod, three laptops, two mobiles and be able to quote verbatim from some W3C/IETF specs and consider oneself a Luddite unless one significantly bends the definition of Luddite."
Re: Google Docs vs manual typewriter
#8Admittedly I couldn't stand to read the whole article. His obsession with typewriters seems to have influenced his taste in font size and family. My question to others based on what I read is how many people here, without looking, can type quickly and accurately but choose to not follow the homerow practice? I type very quickly, and hardly ever need to press backspace. I usually only look when I type in 16 character…
It turns out he is a vimmer. I fully support his argument.
BTW there is even a snippet/plugin that turns VIM into a typewriter by disabling any movement keys.
Re: Google Docs vs manual typewriter
#9Sorry, I had to close the page after reading: "I'm not sure that it's possible to know how to code in as many programming languages as I do" tldr: It's painfully apparent the author is getting too old to Keep Up and is taking that frustration out on newer technology. Retire already. No one uses gopher or typewriters anymore (for serious work), nor will they ever.
You should have at least finished the sentence before concluding that it makes no sense. "I'm not sure that it's possible to know how to code in as many programming languages as I do, own an iPod, three laptops, two mobiles and be able to quote verbatim from some W3C/IETF specs and consider oneself a Luddite unless one significantly bends the definition of Luddite."
Perhaps you're right. I just felt it didn't make any sense. How is owning gadgets and quoting specs some kind of "anti luddite" badge? Seems like he's in some serious denial.
Re: Google Docs vs manual typewriter
#10Admittedly I couldn't stand to read the whole article. His obsession with typewriters seems to have influenced his taste in font size and family. My question to others based on what I read is how many people here, without looking, can type quickly and accurately but choose to not follow the homerow practice? I type very quickly, and hardly ever need to press backspace. I usually only look when I type in 16 character…
On most keyboards it is very hard to touch-type while programming. Seriously, I just can't enter a curly brace while keeping my hands on the home row. It hurts :) And once you move that hand, repositioning it takes time. The other reason I never learned to type properly is that I just get bored. I tried several times, and always gave up. It just feels like a waste typing fjfjfjfjfjfj when I could be entering code. Fi…
>It's how well they think, which is mostly inversely related to WPM.
That's an...interesting claim. Why do you think typing ability is negatively correlated with intelligence?