3 ms·
> Most often these objectives are very clear to the rest of the team. > Also I can’t believe you “know” something is “important enough to interrupt them” > “j
by iateanapple 6y ago
> Most often these objectives are very clear to the rest of the team.
> 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?
- DevKoala 6y agoWhen the objectives are clear, we understand our priorities, and there is very little reason for interruption. Today for example, outside of meetings, I don’t think I communicated with a single coworker. I had a few 1-1’s for pair programming, and those were scheduled during standup. Is your organization aware of studies on interruption? It seems nobody understand the problem. https://www.gamasutra.com/view/feature/190891/programmer_interrupted.php?print=1 https://www.gamasutra.com/view/feature/190891/programmer_int...