This seems to acheive the exact opposite of what the author wants to achieve. If you create a small window of meeting time you are going to end up with any meet

This seems to acheive the exact opposite of what the author wants to achieve. If you create a small window of meeting time you are going to end up with any meeting of more than 3 people violating atleast one person's constraints. I think it goes to the core problem that meetings are the point at which an engineer actually has to acknowledge other people exist and have their own needs. If you are the type of person that needs deep, uninterrupted time that's fine - block out the time you need. But if you over-constrain your calendar you're creating huge headaches for the people who want to meet with you. Who wants to meet with you? Your boss, your product managers, your sales people, your project planners. All people who are going to dictate how useful your "Deep Work" is, all people who are going to be talking to your boss about your performance. I've seen so many senior engineers so wrapped up in their small area of focus they've completly forgotten there's an enormous company around them that's meant to be telling you what the product needs to look like and selling it. Your value to your company isn't measured in git commits. It's measured in revenue.