This is true for the sort of engineers who have no input on what is being built. Once you get to the level where you're making architecture decisions you need meetings in order to discover what to build.
My advice to any developer who dislikes meetings and sees them as an imposition is to find a way to appreciate them, or stay near the bottom of the food chain.
> This is true for the sort of engineers who have no input on what is being built.
It's true for everyone who isn't gratuitously satisfying a desire for social dominance displays.
> Once you get to the level where you're making architecture decisions you need meetings in order to discover what to build.
Some meetings are necessary, all meetings are impositions. If you are at the level where meetings are serving your individual needs and you are calling them, you need to be very cognizant that they are still impositions, and not just for engineers. And it's good to view even your own meetings as a kind of self-imposition to be optimized and minimized in your own interest, as well as those of the other people they are imposed on.
> My advice to any developer who dislikes meetings and sees them as an imposition is to find a way to appreciate them, or stay near the bottom of the food chain.
IME, people high up in the food chain tend to also view meetings as impositions, and people who don't view meetings that way tend to get negatively noticed for it from above, below, and laterally.
The meetings I am talking about are daily stand-ups, presentation for management (why don't you make some slides that we can present to the VP), the random late meeting set by a Product Manager because they wasted too much time on "other commitments" and could only get back to this one now.
As the saying goes, "I would sling code all day for free. It's the other bullshit that I need to be paid a lot for."
Management really should be thin layers in software companies. Instead, it is the only way to progress in the career ladder sometimes. Every manager in this thick layer wants to somehow show that they are doing something. They do this by creating more bureaucracy and busy work (but only for others).
Meetings actually counts as work for them. When they have a hundred meetings a week, they are happy and proud that they worked so much. For engineers/developers (or anyone producing the actual output), meetings are an imposition.