I think you have to separate the I from the O. Output, i.e. typing, is not a bottleneck. Input, that is domain and API research, can be a huge one, especially i

I think you have to separate the I from the O. Output, i.e. typing, is not a bottleneck. Input, that is domain and API research, can be a huge one, especially if you're a "full-stack" or generalist engineer where task switches cause information to get swapped out all the time. If you only have to do a task once every few months, you're going to struggle with retention. 'CPU-bound' I would say is where you have all the pieces you need to solve a problem, but the precise solution is tricksy or math-heavy. Such problems are relatively rare in day-to-day programming. So I would say that on the contary, most programmers are I/O bound most of the time.