Coding is something you can do for longer stretches as you get better at it. I struggle with 3 or 4 hours straight out of college. Now I run 7 hours no problem.

The dichotomy is that the more proficient you are at coding, the more meetings you need to be in to give engineering input... So the less time you spend coding. As a staff SWE I'm rarely able to get more than 3 or 4 hours straight to sit and code. Rather it's an hour here or there broken up my meetings.

I relish my no-meeting days to sit and actually get concepts out into code.

I'm spent at the end of 7 hours coding though. I've crunched to 14 before... But the code I wrote was shit for 5 of those hours.

If my time would be better spent coding than being in the meeting I just decline. It depends on the culture of the org though if that kind of approach is ok or not.