When working remotely think ahead and assume your issue/question isn’t as important as you think it is. Because most of the time questions for colleagues aren't as urgent for anyone except you.
Most of the time the communication is within the team and we do know the other team members situations (work wise).
And we have decided it is important enough to interrupt them.
And we are mostly knowledge workers who understand the cost of interruptions.
Yes, there are bad eggs who waste everyone’s time, but they are in the small minority.
What I find happens a lot is devs focus on their personal productivity ahead of the teams productivity.
Also I can’t believe you “know” something is “important enough to interrupt them”. I work for a place in which the most “junior” dev is worth a quarter of a million dollars a year. I am not going to tell some dude who is probably figuring out a new way to pack data to save us thousands of dollars a day, to take a minute to listen to me. It better be a fire.
> Also I can’t believe you “know” something is “important enough to interrupt them”
> “junior” dev is worth a quarter of a million dollars a year
So the objectives of what you are working on are very clear and yet your very highly paid colleagues aren’t responsible or sensible enough to understand when it’s appropriate to interrupt you?
https://www.gamasutra.com/view/feature/190891/programmer_int...
Because at the end of the day most managers aren’t really concerned with productivity - it’s far easier and less emotionally draining to just proscribe blanket bans.
That’s one of the main reasons remote working hasn’t taken off more.