The sad reality for devs :/

If I see it correctly, the person who attends 16-20 hrs meetings and spends 1-3 hrs coding gets 135k yearly, this is fucked up and dope at the same time.

If you become a senior dev or department head, you usually spend less time on code, and more on reviews, refinement, coaching — so it makes sense.

The idea of 20h+/w of meetings is suicide inducing though.

@sam9669 I'd say that those charts show data for different IT specialisations with only partial overlap. Just look at the max income levels: coding 135k and meetings 160k. If you spend more time in meetings then you are probably higher up (team leader, solution architect, etc.) in IT hierarchy so you get paid more.

It is also interesting what is included in 'coding' - writing code only? Designing architecture? Building experimental PoCs?

I would also like to see a code retention chart. A programmer producing code in one hour that needs no further optimisation and remains part of the product for its lifecycle is more valuable than one who produces 10 times more code in 5 hours 90% of of which must be modified or discarded in later stages. I am not saying that everything is fair and all is right with the world, but the above charts can be misleading.

If this statistics is right although theoretically half the interested dev for this poll were unavailable for long working hours, I will attend more meetings from now on. I don't have one I'll make one up with my manager or coworkers.

don't fucking know how to read these statistics

When I worked at a large company, I had meetings every day and never got to code. Also got paid peanuts.
Now at a start-up I only have one meeting a week, code 9-5 and get paid loads.

Do this survey in India and you'll find some 168 hours a week category over there in the bloody chart...