I wouldn't conflate all the different talking points. Environments are different, the number and scope of interruptions are different. No one who knows what t

I wouldn't conflate all the different talking points. Environments are different, the number and scope of interruptions are different. No one who knows what they're talking about would debate that engineers need large blocks of uninterrupted time to get anything done. But at the same time, not all software projects can be divided up in such a way that individual engineers can just do their thing without frequent communication. This is the whole art of large scale software development, and it is incredibly difficult to get right. Minimizing overall meeting time so ICs can focus is just one consideration, you also need to make sure the right people have a seat at the table for certain decisions or you run the risk of building entirely the wrong thing. As an engineer you have to fight for your own time, but also trade off against the greater good. If you put your work on a pedestal above everyone else around you (designers and product managers are also ICs that need focus time) then you'll hit a ceiling in terms of the impact you can drive (unless you are a researcher or deep specialist, but those roles are comparatively rare).