Many software developers value deep work time—those long stretches where they can get into a flow and really concentrate. But meetings, especially in today’s remote work world, often break that focus. Managers love meetings because they keep teams coordinated, but for developers, they can be a huge interruption.

Paul Graham, a well-known figure in the tech world, has an essay called “Maker’s Schedule, Manager’s Schedule” that explains this difference well. Managers tend to organize their days around meetings, which fit their need for quick updates and coordination. Developers, however, prefer large blocks of time to code without interruption.

During the pandemic, remote work became the norm. Tools like Zoom made meetings easier to schedule and join. While that was convenient, it also meant meetings could be scheduled more frequently and with less effort. Before, you’d need to walk to a conference room, which naturally limited how many meetings you could have. Now, clicking a button can bring ten people into a meeting instantly.

This ease of scheduling has led to a cultural shift. Many developers found themselves in back-to-back meetings, often with no clear agenda. These interruptions break their concentration and make it hard to produce quality work. When you’re building something complex, like a house of cards, even a small nudge can topple everything.

Zoom isn’t evil. It’s just a tool. But tools influence culture. With Zoom, it’s too easy to call a meeting on a whim or add people who don’t need to be there. For developers, this means more context-switching, which kills productivity. A quick 15-minute meeting can wipe out hours of focused work.

Developers need to push back a little. They should communicate to managers that large, uninterrupted blocks of time are essential for success. Using chat apps like Slack can help because they support asynchronous communication. Developers can respond when they’re ready, not when a meeting is scheduled.

It’s also a good idea for developers to block off chunks of time on their calendars. Managers should respect these blocks and keep meetings to a minimum. When meetings are necessary, they should be scheduled at the start or end of the day—times when they’re less disruptive. Some companies even declare entire days or weeks as “No meeting zones” to protect deep work.

Most of us know that meetings often don’t add much value. They tend to be too long, involve too many people, or lack a clear purpose. Developers, in particular, understand this well. Their ability to work in a flow state is precious, and interruptions are like a storm blowing through a fragile house of cards.

Zoom and other meeting tools aren’t inherently bad. They’re just part of a broader cultural shift. If we want to do our best work, we need to be intentional about how we use these tools and protect our focus. That way, we can keep building those houses of cards without them tumbling down at the first gust of a meeting.

Inspired by

• https://www.infoworld.com/article/4072346/zoom-dooms-the-developers-afternoon.html

Sources

• gmpg.org
• paulgraham.com
• ycombinator.com
• paulgraham.com
• nickhodges.com