[bob1029]

I don't know about infuriating but I share your perspective.

At the end of the day, most of us expect to get paid for the code we write. At some level, there is a customer who is ultimately paying for this code. You need to communicate with them via some means or you won't be able to do your job effectively. Either you talk to your team on some recurring/ad-hoc basis, or you get to talk to the end customers directly.

Which one would HN prefer? Filtered internal comms channels where you get to whine and moan about basically everything, or the direct fire of the actual customer where everything is on their terms always? What would ruin your "flow" more? A boring 30 minute call where you were informed the customer is "not happy" or a 2 hour, unfiltered rant session from the live customer?

[sylens]

I don't think anybody is suggesting elimination of all synchronous meetings from a workday. There should just be preference given to long, uninterrupted blocks of time where deep work can be done. Many teams even have a single day of the week dedicated to "no meetings" now to provide makers with at least one guaranteed day for deep work.