I think it was part of the management culture and how they got things "done" back in the day. The CEO came from a background where solution finding was sticking people in a war room for hours churning through things to find solutions. That works when you're sitting together analyzing data but not when you're writing the code to create the data being analyzed.

It also comes from time valuation. They value their work at $X and my work at $K where X > K so it's oK to burn my $K value because the $X-$K delta is high enough to justify prioritizing their work needs.

Another trend I've seen emerging is devs almost always bring in their laptops to meeting and zone out (doing their real work) when they don't care about what's being discussed. Don't know if its good or bad. Or maybe people now even expect you to bring your laptops in case you don't have any input.

Sounds nice in theory but the managers set the meeting.

What they never seem to realise is a 2 hour meeting with 10 people means they use two hours of their time and 20 hours of their subordinates, most of which is spent waiting for the other 9 to finish.

Lots of those managers simply don't see the inefficiency since from their point of view it looks OK.

My theory pertaining to non-technical supervisory staff is that meetings for some fill up an otherwise very empty day. All the technical managers that I have worked for never seemed too eager for meetings - they were too busy building real things to waste time in meetings.

"If you have 3+ hour meetings that sounds like a bug."

Not to management :(

"Maybe figure out why they take so long or why there are so many and address that."

Cause meetings, especially long meetings, are how management shows that they're on top of something and getting things done.

> Maybe get fewer people in the meeting? Push as much discussion as possible out of the meeting so it only involves the people who care? More delegation and indirection?

Totally with you here. I also make it mandatory that everyone coming to a meeting read the offline discussion before hand. When someone shows up and we have to summarize the back history again it is selfishly wasting everyones time. I finally started refusing to do it and will leave and tell the PM to reschedule.

Yeah, we have an open-office plan, but we've successfully lobbied to have developer meetings largely moved to one day a week, and engineers on important projects get "office hours" to allow for interruptions during a defined time. It's important to separate meeting cultures from open offices.