I wholeheartedly agree and find it relevant to mention PG's article on the subject: http://www.paulgraham.com/makersschedule.html
Re:Why developers hate being interrupted
by dllthomas on Wednesday January 07, 2015 @12:54AM
(#8849114)
"Impromptu status pings, except in a production crisis or in a time-critical situation, shouldn't happen."
I have the urge to weaken that, when the status has material impact on what the ping-er should be doing. If my coworker - superior or otherwise - is trying to figure out what he should be telling our most important customer that's a different thing then him just wanting to know - or worse, thinking it's keeping me on task.
Thoughts from your PoV?
Re:Why developers hate being interrupted
by michaelochurch on Thursday January 08, 2015 @12:09PM
(#8857358)
I agree. The first rule is that there are no rules. If you need to interrupt someone to get unblocked, that's different from asking for a general status report. I was talking about the latter.
Impromptu status pings, except in a production crisis or in a time-critical situation, shouldn't happen. Any status reporting infrastructure should be regular, legible, and structured and, in typical times, ought to consume no more than 15 minutes per day.
As for meetings, those can be useful or worse than useless, and the problem there is that the usually higher social status of those who schedule them prevents proper feedback on the meetings that don't work or make sense. Just as there's complexity creep in code as features (whether well-thought-out) pile on and kludges and counter-kludges are thrown in, there's complexity creep in management as meetings get thrown on calendars and the people most aware of them not working don't feel comfortable pointing the fact out.