4 ms·

Having also been a remote developer your reaction is extreme. There are definitely times where people weren't available within 5 minutes, but if that were the n

• Swizec 14y ago
  I really really don't like going through a 20+ minute interruption cycle every time somebody needs me for two minutes. 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.
• ankitml 14y ago
  As a developer, you either work or you communicate. Try multitasking and your productivity drops. This is not an opinion, but a hard truth that our minds are not meant for multitasking. 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.