Tech Columnists' Day Without Email
Carl Bialik from the WSJ writes "When a recent power outage disrupted email service at WSJ.com, our tech columnists were plunged backwards into a time before every meeting, every little task, came with an email-program reminder, and where checking the bottom right of the screen for a new-mail envelope was futile. "Some of us quickly got a reminder that email is the lingua franca of projects that bridge different departments and involve a lot of people," Tim Hanrahan and Jason Fry write. "For all the talk of whiteboarding, it's email threads that we rely on to remember where we left certain questions and what our next moves are. Similarly, email has become our storage system for important documents and works in progress--how often do you email yourself? It's also replaced the telephone for lots of our routine touching base between colleagues, friends and families: Instant messaging is simultaneously too casual and too intrusive, and weekday phoning is reserved for more-substantive matters and emergencies. So a lot of that social lubrication went out the window.""
our tech columnists were plunged backwards into a time before every meeting, every little task, came with an email-program reminder
Ah, well that explains the recent tech rumor flurry then; the WSJ had simply been transported back in time to 1996, when Apple was dying
Remind me not to work someplace where they promote "Social lubrication".
The first step is to admit that you have a problem.
-CausticPuppy "Of all the people I know, you're certainly one of them." -Somebody I don't know
Without reading the article and knowing precisely what the story was, I would say that they all cracked eachother's heads open and feasted on the goo inside.
This explains how the WSJ missed Steve Jobs' e-mail saying "we're not moving to Intel, jackasses!"
mbbac
Does anyone else take a deep breath before clicking on one of these links at work?
How would productivity be affected if /. was down for a day?
The Internet is full. Go Away!!!
That would be difficult without power. Unless, by "instant messenging", you mean you write down a message and a hamster instantly runs along the hall with it to its destination. Hmm, I might be on to something.
the layman's guide to computer science
Once he'd got the employees up and running with telephones we let them try it out. It all seemed fine to start with: The telephone system was a pretty good replacement for those shitty Eudora boxes we'd used before and the employees could still do their work as normal.
Alas it did not stay that way. After a few days, I had lost count of the number of complaints received from our employees. Users could not do things they could before (like manage their contacts). The final straw came when one employee lost several hours work when the PBX suddenly froze up, effectively destroying our communication infrastructure.
Needless to say, the community offered no support whatsoever. I made the employee destroy the telephone system and lets just say he's not with us anymore.