3 ms·
The thing I like best about this is that I basically never have to wait for somebody to get back to me. But what about the person in the middle of "flow" th
by damncabbage 15y ago
The thing I like best about this is that I basically never
have to wait for somebody to get back to me.
But what about the person in the middle of "flow" that you just asked a question?
- wpietri 15y agoThe person I most often have to talk to is a product person, who are happy to be interrupted most of the time (and when they aren't, they go hide). When it's another developer, there's an etiquette to it. Because we're in the same room, I generally know when they're focused, and will just wait a bit if it isn't urgent. You also have graduated options for interrupting. There are times when people get my attention just by looking at me, or turning towards me and waiting a moment. If somebody is in flow, they'll probably ignore that. We also do test-driven development and a fair bit of pair programming, which makes distractions less problematic when they do happen.
- lawnchair_larry 15y agoYep, that's why I can't stand this arrangement. Respect others time and workflow by using non-blocking communication like email or IM. They'll answer when it's convenient for them.
- dkersten 15y agoI always preferred IM or email to phone or face-to-face for this exact reason. IM and email can be ignored until its convenient to reply, but phone and face-to-face forces you to stop working and respond right away, even if you were right in the middle of something.