News for hackers. Stuff that matters.
Re:Jason Fried: Why You Can’t Work at Work [video] by patrickryan on Monday March 29, 2010 @10:15PM (#1228159)
This was basically his Startup School talk. He definitely has many great points but I question a few. Such as, using IM as a replacement for speaking directly to a coworker within an office. How can this be more efficient? I don't see it.
Re:Jason Fried: Why You Can’t Work at Work [video] by hboon on Monday March 29, 2010 @11:19PM (#1228254)
I didn't watch the video, but you can ignore IMs or reply to them later, not unlike emails, but much less so when someone is talking to you face to face.
Re:Jason Fried: Why You Can’t Work at Work [video] by CitizenKane on Monday March 29, 2010 @11:53PM (#1228318)
I have a job where the office is IRC. Right out of the gate, using chat isn't more efficient. But after a period of adjustment, I would say about a month it becomes natural and just as efficient in most cases as having a face to face conversation.

I would say where it doesn't work well is when you need to discuss a lot of details. I think having meetings occasionally (on the phone or face to face) makes sense. It help gives a broader view on the project. I think Jason is referring more to having meetings every day. Often it simply isn't useful.

Re:Jason Fried: Why You Can’t Work at Work [video] by hopeless on Tuesday March 30, 2010 @06:21AM (#1228750)
Much of our collaboration/communication is done over IM. The problem with IM is that they still expect a reasonably instant reply. Sure, you can ignore it but then you'll just get an email and/or a phone call.

As a preference though, I prefer to talk to people face-to-face so you can see if they're too busy/stressed etc.

Re:Jason Fried: Why You Can’t Work at Work [video] by astrec on Monday March 29, 2010 @11:09PM (#1228243)
Asynchronous communication, including IM, is usually more efficient than interruption iff the question of the moment is not urgent (in the truest sense) and the recipient is busily engaged in getting other things done. <insert I/O analogy of your choice here>.