> How many threads have been posted on HN complaining about things that take programmers out of their state of "flow"? How many programmers have you met who are

> How many threads have been posted on HN complaining about things that take programmers out of their state of "flow"? How many programmers have you met who are happy to hear their phone ring when they're working? Those are what the true interruptions are about. A notification? I'm sorry, but after less than a month one learns how not to let a simple sound or notification distract you. Constant phone ringing is a true interruption; one ringing loop? Not so much. > 2-3 years studded with bouts of lost productivity is a lot of lost productivity. A product that tells me my life is "only" going to suck for 2-3 years while I learn how to use it is not a product I am going to be thrilled to use. Handling interruptions is about not letting them make you lose much productivity, but after all, this is for true interruptions. They will affect you, but there are ways to lessen the effect. If people allow other people to constantly interrupt them without setting clear boundaries/priorities, it's your (or your Manager) problem. I usually set things in the clear from the beginning, and after two or three times, it'll never happen again. But again, these are true interruptions: Some are necessary, and those which are not can be handled better.