Also, you must account for no-interruption working blocks. You must be able to take at least 30 minutes w/out having to answer any IM in order to get sh*t done. That's the main reason why 37signals built Campfire in the first place...
When someone's working solo, they still use Campfire to announce what they're doing/thinking: "refactored widget X", "Think I have that validation working". It helps us all understand what's going on. Some of that is just primate grooming behaviour, but we're still primates, so it's useful.
For example, for me a phone call is something that prefers a quick response, an IM message can wait for some time, and a bugtracker ticket or an email is "I'll reply when I'll have time to do it".
Quite possibly the worst piece of productivity advice I've ever seen. Given that if you're concentrating on a task it takes more than that amount of time to get back your train of thought, if you're doing this regularly during the day you'll get almost zero work done.
In real life, if I have a critical bug that falls into remote dev's domain, he'd better be damn sure to take his headphones off and get back pronto. Because that's exactly what would've happened if he were sitting across the room.
Nobody expects a telecommuter to answer right away, but quickly acknowledging a question is a rudimentary communication requirement that goes a long way in building functional team. The "I will get back to you within 24 hours" provision from the linked article is as laughable as it is absolutely ridiculous.
Being able to talk to people immediately is critical.
(I've been running a remote team for 5 years)
If your units of work are so badly partitioned that this is a requirement, remote or local is not really the problem.
Since these things are often necessary, you need to be able to have that happen in a remote environment.
I agree with you though on one important thing - issues of interruption have little to do with remote/local. I try to interrupt people as little as possible either way, but I don't want remote working to sacrifice on real time communication when necessary.
Screw you, even if I was sitting right next to you, you have no right to expect a response to your query in a minute. I will get to you when it's the appropriate moment in my workflow, otherwise I'm just running around like a headless chicken all day getting nothing done.
Working time is headphones on time. You do not distract me when my headphones are on.
We are not doctors in an operating room, you can wait 20 minutes. Hell, if I let you wait 20 minutes there's a 90% chance you'll solve the problem without me.
Acknowledging communication can also be: "I'll be with you in 20 minutes". That gives me the option to (in 95% percent of the cases) respond with "cool" and plan my own time accordingly, and in 5% of the cases to respond with "sorry, we really need to deal with this now, and here's why".
How fast you respond when someone tries to communicate with you has very little to do with remote/local. I love remote environments, they have huge upsides. Not being able to go to real time when necessary though is a major problem.
Secondly, if someone interrupts you during a highly focused session of coding, there is no way you would reach same session immediately after interruption.
Think of it as Inturruptability Quotient for every task. It can be roughly defined as ratio of time required to reach same state as before to the time required to finish the job. There are some tasks like writing documentation or editing a proposal, where you can reach similar state of mind as you were before interruption fairly quickly.
However for tasks like programming, designing a db or simply thinking abut a hard problem can take even hours to reach the same level. Inturruptability Quotient is sufficiently high here, maybe more than 1 sometimes. Do you even realize how much grave damage it does to productivity.
I would much rather devote a solid 20 minutes, even an hour, to you than half-arsedly devote 20 minutes spread out over 10 hours in one minute chunks.
Generally though, you can count on being able to talk to someone when you walk up to their station. When running a remote team, I want people to generally "be around". We work very closely together though, so maybe our needs are not a good example.
Acknowledge any inquiry within 5-10 minutes unless on a lunch break. Otherwise it means you are afk.
(edit) To elaborate - there are two issues involved with this. First is that you are unlikely to ever work on a fully self-contained task that doesn't require collaboration with other people. As such having shared work hours is required. Second issue is that of trust. In common tongue "working from home" means "sleeping in, sitting on a couch, going for two hour lunch breaks, etc". It's a way to slack while pretending to be working. I'm working from home, wink, wink, quote-unquote. In a perfect world you would be judged on deliverables and perfectly met deadlines. In real world, you will frequently need to prove that you've been working and that 1 page of code has indeed been a result of a week of research and numerous rewrites.