4 ms·
It may not make much difference in laying down the actual code, but it is still a valuable skill for the coder to acquire. If you can touch type you're more lik
by leephillips 12y ago
It may not make much difference in laying down the actual code, but it is still a valuable skill for the coder to acquire. If you can touch type you're more likely to write useful comments, documentation, and notes. I suspect the subconscious barrier to writing these small but essential bits of prose is larger in the non-typist. You'll write better commit messages, and will be more likely to turn your notes into online articles to share your code and ideas.
- Roboprog 12y agoYes, and autocomplete won't help on this. I would also argue that the touch typist is more likely to come up with names like rowIdx (row_idx), colIdx, rowLimit, colLimit, findMatchingRow(), rather than (always punting to) names like i, j, m, n, scan().
- danso 12y agoThis is a great, often-overlooked insight: when there is considerable friction in doing something, you will often not only be slower, but you will do something in a decidedly counterproductive fashion. So it's not always accurate to use the XKCD comic Is It Worth the Time? (http://xkcd.com/1205/ http://xkcd.com/1205/) as a metric...efficiency can't always be measured in seconds/minutes shaved * number of times action is performed...because when it's easy to do something, it's easy to explore...and also, it's easy to follow best practices. Of course, the other side of it is...even if something does result in a large number of minutes/seconds shaved, you have to consider the opportunity cost of you spending your time implementing an automated system...and at certain early stages in a startup lifecycle, that premature optimization time can be fatal.