I dont think it is generally vigalanty programmers, just that routinely and irregularly interrupting knowledge workers is counterproductive. Like, I've been deb

I dont think it is generally vigalanty programmers, just that routinely and irregularly interrupting knowledge workers is counterproductive. Like, I've been debugging and researching a potential bug and I'm deep in thought about it, then a manager or PM walks up, interrupts your train of thought with something completely unrelated to what you're currently working on. Context switches are annoying to the engineer and costly for development. Each context switch probably costs between at least 15 to 30 minutes, maybe more depending on what the engineer is working on. If that happens 4-6 times a day, you've potentially burned 1/4-1/3 of the day. I spent close to 3 hours in 3 unrelated meetings. So, 1/2 of my day was spent task switching and not really giving 100% attention in the meetings because of the constant task switches. Frustrating and don't feel like I made any progress today, on my first day back on an overdue week long vacation.