3 ms·
The thing is, when a programmers starts to generate input, the problem is already solved, he is merely putting the solution into whatever representation the too
by usrbinbash 5y ago
The thing is, when a programmers starts to generate input, the problem is already solved, he is merely putting the solution into whatever representation the tools demand.
I am not defending 10-15 WPM here ofc. just statingt that the majority of work happens before we start typing in code, and after we typed it.
- foxfluff 5y agoIt's a type-think-type-think cycle (or type-test-think-type-...) and the more time and effort you spend on the typing part, the more it distracts you from the rest. Typing for a few minutes isn't any better than compiling for a few minutes before you can test. It just interrupts the more interesting work.
- usrbinbash 5y ago> It's a type-think-type-think cycle Depends entirely on the individual developer. For me its think-think-think-think-drinkcoffee-think-type. And after the first iteration, the typing to make changes is usually miniscule compared to the initial amount.