I fully support the sentiment here, and took a lot of the content from Deep Work to heart when I first read it and was trying to figure out how to be a more pro

I fully support the sentiment here, and took a lot of the content from Deep Work to heart when I first read it and was trying to figure out how to be a more productive professional SWE, but a lot of this information is common knowledge within SWE culture for those who care about it, and I still haven't found an organization or team that actually puts these into practice. I fear we've already lost this battle and the non-knowledge-worker to knowledge-worker ratio has gotten too high for tech companies/workers to get the cat back in the bag. If anybody has successfully changed a dev team's processes to make changes in the right direction, I'd love to hear how that happened for you. Many people I work with complain about too many meetings and interruptions and yet the expectations which contribute to these problems continue. My org recently adopted having a "no meeting day" every week and without this I don't think I'd ever get anything done.