I'd say 85-90% of my work these days is programming. Both the actual coding and thinking through problems or architecture decisions, benchmarking, testing/compa

I'd say 85-90% of my work these days is programming. Both the actual coding and thinking through problems or architecture decisions, benchmarking, testing/comparing approaches, etc. It really depends on the position and nature of the responsibilities though. I've had position where at least half my time was meetings, and others where there was just a lot of Slack chatter to work through during the day. Right now I'm on a limited-time contract with a very specific project to iterate on and finish up, so I don't get pulled into peripheral company decision meetings, 1-1s, etc as much. This appears nicely conducive to programming time.