4 ms·
In a corruption of a Steve Yegge saying, most programmers are CPU-bound rather than I/O-bound. Very rarely has my code typing speed inhibited my productivity. U
by jogjayr 8y ago
In a corruption of a Steve Yegge saying, most programmers are CPU-bound rather than I/O-bound. Very rarely has my code typing speed inhibited my productivity. Understanding which problem I need to solve, and doing the research takes up the bulk of my programming time. Actually writing the code is a formality after that.
- dTal 8y agoI 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.
- seventhtiger 8y agoI don't think memorizing is to type faster. It's to think faster. CPUs speed up with more cache. Adding in a websearch/API lookup in-between thoughts will slow a programmer down.