Being able to change code and deploy immediately (or in a few minutes) matters immensely.
This might just be feedback loops at an extreme, but I believe it’s something more.
The benefit of going from 20wpm to 40wpm was not ×2 to my writing and experience, it was more like ×8. I fully intend to reach 60wpm.
It was closer to a ×2 to my developing experience, which is interesting as most of software development isn’t the actual typing.
Another anecdote is that the best programmers I know all have 60+wpm (there was one react front end guy who was good, but mostly at design).
Reducing friction is underrated, even if friction is only 10% of a job (typing during coding), improving that friction substantially matters more than 10%.
This may have to do with flow, concentration or enjoyment
Devops Mentality is correct:
Friction is a big deal.
Being able to change code and deploy immediately (or in a few minutes) matters immensely.
This might just be feedback loops at an extreme, but I believe it’s something more.
The benefit of going from 20wpm to 40wpm was not ×2 to my writing and experience, it was more like ×8. I fully intend to reach 60wpm.
It was closer to a ×2 to my developing experience, which is interesting as most of software development isn’t the actual typing. Another anecdote is that the best programmers I know all have 60+wpm (there was one react front end guy who was good, but mostly at design).
Reducing friction is underrated, even if friction is only 10% of a job (typing during coding), improving that friction substantially matters more than 10%.
This may have to do with flow, concentration or enjoyment