What a developer thinks, but not what managers who actually sees the forest through the trees think.
The guy who knows what he is going off and does his thing. No one meets or talk. Developers later finds out someone else was doing the same thing or solved the same problem.
Meetings can increase productivity if they have a point, use some kind of software to manage work originating from (like Trello), and have general rules.
You can take my daily standup meeting from my cold dead hands.
Bad meetings are just that. It's like people who hate government not being good at running a government. Since you demise them so much you probably go in with a super negative attitude about them. You doom yourself and your team to fail. I've seen meeting make measurable improvement, watch the meeting stop happening because of it, and then watch it revert, rinse repeat...not a horrible approach at the end of the day. Syssies with developers, developers with qa, etc. etc.
Productivity claims are just people bitchin...and a lot of it has to do with the simplicity of the product, users, and other measurements. You go into companies with lots of complexity, legacy overhead, needy clients, and you'll end up with low productivity.
And oh yah, don't capitalize meetings. It only shows your immaturity. Claiming that other people don't know what they are doing and that you do is also pretty cocky...I'm sure you know everything right? Come on slashdot stop being so reactionary.
Marketing is the only group that are bigger divas then developers these days. Relax your not nearly as smart as you think you are...you are just used to people telling you are because you like math.