Slashdot Mirror
Slashdot Asks: How Do You Handle Interruptions At Work?
This question was inspired by this anonymous submission:
Analysis of programming sessions and surveys note that programmers take 10-15 minutes to resume editing code after being interrupted. Computer scientists and researchers from University of Zurich and ABB Inc. have designed the 'FlowLight' system which automatically determines a worker's interruptibility using a combination of keyboard/mouse usage, calendar information, and login state, and makes interruptibility visible to other employees using a red/yellow/green LED indicator placed near the desk... Knowledge workers in various locations found that interruptions were significantly reduced by 46%. [PDF]
NBC reports these researchers "also tested a more advanced version that uses biometric sensors to detect heart rate variability, pupil dilation, eye blinks or even brainwave activity," and of course one of the researchers tells the New Yorker that a commercial version "is 'in the works.'" But it'd be interesting to hear from Slashdot's readers about their own solutions -- and how interruptions affect their own productivity at work. So share your best answers in the comments. How do you feel about interrupt
NBC reports these researchers "also tested a more advanced version that uses biometric sensors to detect heart rate variability, pupil dilation, eye blinks or even brainwave activity," and of course one of the researchers tells the New Yorker that a commercial version "is 'in the works.'" But it'd be interesting to hear from Slashdot's readers about their own solutions -- and how interruptions affect their own productivity at work. So share your best answers in the comments. How do you feel about interrupt
What the article doesn't factor in is the time lost by the interrupter if he/she doesn't get the help/answer in a timely manner.
Perhaps because most really important questions aren't the type where in order to prevent the terrorists from blowing up New York, you have to waterboard right now.
If it's important, it should have either been dealt with or considered over a long enough time frame that they can fit into the programmer's schedule. If it's a "where's the source code to 'X'" question, it's the kind of question that indicates that essential corporate information is in someone's head when it should have been shared and documented. If it's a "why does 'X' do 'Y'". an off-the-top answer is probably going to lose something vital.
About the only question I consider interruption-worthy is "Did you realize that the building is on fire?" And sometimes not even then.
Geez, just check when the compiler is running. If it is, I have a few minutes for you. See? This really isn't so hard, is it?
For coders, or anyone in particular, ya gotta remember that your particular job isn't the only, or the most important job at the place.
Because that interruption might be from the guy who signs your paychecks.
For me, it isn't coding, but 3-D work. It's like an alternate universe, and while reducing everything to numbers and juggling it all in my head, I do lose track of reality. And it takes time to come back, then get into the 3-D Universe again.
While my people would "protect" me from interruptions when I was doing that intense work, there were some people who they had to let through. So it was just part of the day.
If any of y'all have a position where you can thell the director or CEO to slag off - you better keep it.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.