Knuth versus Email (1999)
cs.stanford.edu
cs.stanford.edu
The skills and kind of work that makes a person successful at one level often leads to lack of success at another.
They talk at about 2.3 million words per min and a 20 second conversation gets sent back by the exec assistant or one of the reports. Brilliant person, email isn't their forte.
"Is this the most important use of my time" is on their wall. Email isn't it. It works other ways, a voice mail from Hawking isn't the best use of his time.
People tend not to ban things before they're widely used and cause some sort of problem. I imagine there was a time at his company where his executives used computers. People would have a memory of the time before the computer ban, and compare it every day to the time after the computer ban.
These executives probably had stellar track records, had the motivation to do better, had the previous experience of using computers, had political sway, and still failed to convince the CEO.
And yet, with nothing more than a brief description of the abstract idea, and a firm belief that computers are valuable, a Hacker News commenter has been able to diagnose that it's holding their company back.
That's not to say that CEOs can't make bad decisions, but we don't even know what the company does or what they sell. Probably neither of us have worked there. It seems a little premature to rebel at his decision.
I am not on vacation, but I am at the end of a long time delay. I am located somewhere on Earth, but as far as responding to email is concerned, I appear to be well outside the solar system.
After your message arrives at gnu.org, I will collect it in my next batch of incoming mail, some time within the following 24 hours. I will spend much of the following day reading that batch of mail and will come across your message at some point. If I write a response immediately, it will go out in the next outgoing batch--typically around 24 hours after I collected your message, but occasionally sooner or later than that. Please expect a minimum delay of between 24 and 48 hours in receiving a response to your mail to me.
If your message is hard to understand or responding takes real work, the response could take longer.
So please wait 48 hours after sending a message before you resend it, remind me about it, or ask if I have received it. If it has been less than 48 hours, the absence of a response from me only means you have not given me time to answer.
If you are having a conversation with me, please keep in mind that each message you receive from me is a response to the mail you sent 24 to 48 hours earlier, and when writing it, I probably had not yet downloaded your later mail.
If you are in big hurry to speak with me, and one day's delay would be a serious problem, you can ask my FSF assistant to phone me. Send mail to <rms-assist@fsf.org> saying what you would like to talk with me about, and giving your telephone number. You can also call the Free Software Foundation office at 617-542-5942 (weekday Boston business hours) and ask them to phone me on your behalf. If it's really important, try both!
An intermediate measure is to email me your phone number and ask me to phone you.
But if there isn't enough hurry to warrant phoning me, please don't bother the FSF people. The mail you already sent me will reach me before any mail they could send me now on your behalf. I will respond as soon as I can.
To contact the Free Software Foundation, use one of the addresses in https://www.fsf.org/about/contact/email.
If you do not wish to receive this message ever again, please send a message to rms-autoreply-control@gnu.org with the subject "OFF". Otherwise, you might receive a reply like this one up to once a month.
Sometime around 2000, busy people started complaining about this practice, and old timers started to hold their tongues. I knew the era was over when my Millennial co-worker one cube away asked me to not interrupt him and IM him instead, since he had to take off his earphones. About the same time, my boss complained about how long my (senior engineer, explaining matters related to the immanent demise of the company...) emails were -- frankly managers were busy and 1-2 sentence ought to explain about this O-ring problem.
Your projection of self-centeredness on the part of your elders is unbecoming and ill-informed. You are merely young.
rms is just old school.
I find most "short" messages lack key details, requiring me to either search out more information, request a clarification, or abandon the conversation (due to anticipation of the pain continued communication would cause). This is more time and mentally expensive to me than reading a longer more precise message.
Also RMS replies to a lot of the random emails he gets. Much more than a lot of people who are as well known as him to be fair.
Sounds to me like you are just not a big fan of RMS so find a negative in everything he does that isn't quite the norm.
For more on this, see: https://en.wikipedia.org/wiki/UUCP#Mail_routing
https://groups.google.com/a/mysociety.org/forum/#!msg/mysoci...
To people who think like rms, these rules are very helpful, but I think many people will get the impression that he is being very rude by having a long document with his preferences.
If you don't know what you're doing, you won't treat the other party seriously. This is a strong signal to the other party that you don't know what you're doing and SHOULD be avoided.
If -however- you do know what you're doing, then you take the other party seriously even when you come across such demands because (as shawn-furyan said):
> Those sort of riders are a sentinel to signal that the venue read the contract carefully... If they caught the brown M&M's thing, they probably got all the stuff about rigging safety, so you don't have to grill them on those things. Otherwise, you'd better double check.
http://ultimateclassicrock.com/david-lee-roth-van-halen-brow...
This applies to RMS -- when he's on the road, he's often at the mercy of the event organizer for transportation and lodging arrangements (either directly or indirectly by them providing information). If they mess up, he's in real trouble.
Never having met the guy, that doesn't really sound like rms' MO.
If he reaches to YOU, and he still demands that, then that's another story.
>The man certainly has some condescending opinions about software, but he is not conceited about his own celebrity - he quite certainly would gladly give it up if he could.
Which is why he's happy to let Linus get all the credit?…
I'm not accusing Knuth of this, but I think some people just use email as a way of humble-bragging. "I'm so important it's overwhelming!" Yeah wow. We're all so impressed.
That there might be why you haven't learnt to hate Email (or other forms of asynchronous communication). If you want to learn to hate, try running a few mildly successful Open Source projects. Or try participating in other lame company flame email thread.
The fundamental problem with email (and other forms of asynchronous electronic comms including Github pull requests and Facebook messages) is there's little burden on the sender. The entire burden is carried by the recipient. It's too easy for the sender to turn impulse into wasting someone else's time. Snail mail at least costs a stamp and a trip to the letter box.
TLDR: Right now email doesn't scale
The fact that an email is easy to send without knowing the recipient is a huge benefit of email. No other electronic communication system offers this benefit (and unfortunately it enables spam, but that's an entirely different discussion).
For example, when I'm trying to write a tricky piece of code, it goes much better if I can shut out interruptions like Knuth does and concentrate on the task at hand. If people expected me to reply immediately to their non-urgent e-mails, it would be a lot harder to concentrate.
Also, people who expect me to answer their e-mail or phone call immediately are making the presumption that whatever they have to ask me is more important than whatever I currently happen to be doing. In most cases, it's not.
With that said, I certainly recognize the need for very-deep-focus jobs to be uncoupled from the "right-now" pace expectations of email. So I think Knuth is making a smart decision for the kind of work he does (and one that could be useful to other people in similar lines of work), but he's just presenting/explaining it poorly.
It's sorta like the person who proclaims "I don't have internet access, and I'm better off for it", and then goes on to say that they have a personal assistant whose job is to handle all their online accounting/shopping/research/etc for them. Maybe they personally are better off for their particular workflow, but the really are using the internet, just by proxy, and their implied value statement about themselves compared to people who do use the internet (directly) is not really valid.
I made an app that shows you how often you check your email: http://focuslist.co/escape/ (and other distracting websites)
Companies and organizations have not yet grasped the negative impact on productivity that email has wrought. Like drinking from lead goblets in another era, it's going to be a while before we get it. We need email, but it needs to be put in its place.
I sense there's a joke here. Did anyone get it?
Is the use of "versus" in the headline correct in English? There isn't anything adversarial going on here, it is just his email policy.
In other places "versus" even seems to be used as a synonym of "and".
On the contrary, this passage sounds quite hostile:
> If I run across such a message that was misaddressed --- I mean, if the message asks a question instead of reporting an error --- I try not to get angry. I used to just throw all such sheets in the wastebasket. But now I save them for scratch paper, so that I can print test material for The Art of Computer Programming on the blank sides.
Edit: Oh, right, see the summary elsewhere about his secretary Phyllis Winkler at her retirement.
<!-- Changed by: Ursula N. Owen, 8-Mar-1999 -->
It's possible that it's referring to the HTML skeleton, not the article itself.