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.
Comment on Typing is not a programming bottleneck
Anders429@programming.dev 1 year ago
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.
Piatro@programming.dev 1 year ago
Gentoo1337@sh.itjust.works 1 year ago
Same. I think vim and touch typing are more about comfort tbh.
dbilitated@aussie.zone 1 year ago
yeah the issue honestly is how much someone else has to read to understand your code, that’s the issue. 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.
killeronthecorner@lemmy.world 1 year ago
The code that I suggest is too verbose. It involves too much typing.
This seems to be the whole premise and it’s obvious that one does not follow from the other.
Overly verbose code is code that can be expressed more minimally for some benefit. I can think why anyone would argue that one of those benefits is less typing.
The author can solve this easily though: ask them why verbosity is an issue. Then they will know the answer and won’t have to presume something as tenuous as “amount of time spent typing”.
PowerSeries@lemmy.ca 1 year ago
I’ve watched some slow typists program, and I think I have the answer. If it takes you a while to type the code out, you are much more likely to stick to the first approach that works, and not rewrite it as much.