• onlinepersona
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    1 year ago

    I agree with part of the article, because I didn’t read the rest. I truly dislike the use of single letter variable names: f, g, h and foo, bar, baz. My advice: use descriptive variable names.

    function twoIfs, function complicatedIf, var simpleAnd, etc. Makes it so much easier to read examples instead of remembering “oh yeah, f had two ifs in it, h had the if/else, g calls f which calls h which,…”.

    Also see this often in other examples: "A for ‘Truthy variable’ " 😓 Wtf. Laziness is good when it makes things easier, not harder.

    • lysdexicOP
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      8
      ·
      1 year ago

      My advice: use descriptive variable names.

      The article is really not about naming conventions.

      • Sheldan
        link
        fedilink
        arrow-up
        14
        ·
        1 year ago

        Should have still used them. It was harder to read this way.

        • potterman28wxcv@beehaw.org
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Agreed that some people can find it easier with explicit names - however some people find it easier with short meaningless names as it makes them focus on the abstraction rather than the naming. There is no right or wrong here. It all depends on the reader.

        • lad
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I even thought that this (hardness) was intended to emphasize the way it’s hard to spot problems in real codebase 😅

      • onlinepersona
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        1
        ·
        1 year ago

        Doesn’t matter, it’s hard to read an article. If it were hard to read for another reason like bad grammar, I’d comment on that too 🤷