I'm a bit confused about the premise of the article. Does anyone assert that typing speed is a bottleneck at all? I've been in the industry for years, and have never heard that claim.
I do agree about the whole "less code is not always more", but I get confused when the author keeps bringing it back to typing speed.
I've heard the argument as a positive of learning vim and while it did finally force me to touch type I can't say that it had any impact on my programming speed.
yeah the issue honestly is how much someone else has to read to understand your code. it's weird because the whole article is about making readable code for the next person and he never stops to address the fact that leaving 10x as much code to read might also make life more difficult.
I feel like he just wanted to make a point about how it's nice to make types immutable and suggest other techniques can be worth implementing too, which I agree with, but honestly his premise is a trainwreck.
I'm a bit confused about the premise of the article. Does anyone assert that typing speed is a bottleneck at all? I've been in the industry for years, and have never heard that claim.
I do agree about the whole "less code is not always more", but I get confused when the author keeps bringing it back to typing speed.
I've heard the argument as a positive of learning vim and while it did finally force me to touch type I can't say that it had any impact on my programming speed.
yeah the issue honestly is how much someone else has to read to understand your code. it's weird because the whole article is about making readable code for the next person and he never stops to address the fact that leaving 10x as much code to read might also make life more difficult.
I feel like he just wanted to make a point about how it's nice to make types immutable and suggest other techniques can be worth implementing too, which I agree with, but honestly his premise is a trainwreck.