Then raise those issues like an adult, rather than passive-aggressively tuning out.
Then raise those issues like an adult, rather than passive-aggressively tuning out.
> Do you spend far too much working time at meetings? Do you try to make important decisions in groups of more than 10 people? Do you have more than, let’s say, 15 co-workers under your direct management? Do you receive daily reports which you don’t read on the day you get them? Do you have days when you don’t have time to ring back the person who’s been looking for you to discuss an important matter? If the answer to any of these questions is “yes”, then you yourself are part of the problem, because you’re no longer on your guard against ever-increasing bureaucracy.
Unless you're some kind of modern-day ornamental hermit, writing code is unlikely to be the end goal; more likely you're getting paid to produce something useful, something for which communicating and understanding the problem is often far more important than actual coding.
> If I raise the issue everyone gets all pouty.
This does not sound like a healthy working relationship, although I'm not sure the problem's on their end.
> There is an unspoken feeling of being forced to attend every meeting assigned to you just in case something feels useful.
Well, nut up and get over it. Either attend or don't, but don't half-ass it. The surest recipe for pointless meetings that go on for too long is meetings where half the participants are coding instead of paying attention.
Then it's time to move on. This is not a way mature adults should be handling such a situation.
A passive-aggressive reaction isn't mature either though, so maybe this is mutual and your company and you are actually perfectly in tune.