• Anders429@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    11 months 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.

    • PowerSeries@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 months 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.

    • dbilitated@aussie.zone
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      11 months ago

      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.