The way you can tell you're in one of these dysfunctional companies in my experiences is at the moment you, as a software developer, have to attend TWO meetings in one day. Companies that have too many meetings tend to have middle managers with only one goal for all these meetings: "Covering their ass." They treat these meetings as a way to collect evidence to be used later to prove that they weren't at fault when the project fails to meet it's objectives.
I'd say more than 5 meetings a week for an IC rather than two in a day. (I have 3 meetings a week, but two of them are coincidentally on the same day). Managers will naturally have more meetings.
I agree, you're right. I didn't think of it that way because most agile teams have a mandatory scrum meeting in the morning every day anyway. So a meeting is always literally the first thing you do...or at least it's your first interruption that comes right about the time you begin concentrating.
It's super counter-productive too because in the morning is when I'm at my most productive and a guaranteed interruption every single morning is horrible.
> It's super counter-productive too because in the morning is when I'm at my most productive and a guaranteed interruption every single morning is horrible.
At least in my bubble, tech seems to be skewed heavily towards night-owls. I winder if putting the meeting in the morning is due to people assuming that, since they aren't productive in the mornings, neither is anybody else.
In my 20s and 30s I wasn't productive in the morning mainly because chances are I was out half the night drinking. Since hitting my 40s, I'm most productive in the morning, because I'm never out late.
