I don't think the average professional programmer gets to code in much more than 30% of working time. Too much time gets spilled looking at documentation, sitti

I don't think the average professional programmer gets to code in much more than 30% of working time. Too much time gets spilled looking at documentation, sitting in requirements meetings, etc. The problem is more that, to get something done while working 30% of the time, the CTO has to cherry-pick the fun projects where things can be accomplished quickly without the time-consuming slogs. That can cause morale problems if the rest of the team is spending a lot of time on slogs. One might argue that that's a sign of a deeper problem, but few companies have figured out how not to generate drudge work when at significant scale.