• PoastRotato@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    My coworker flips his shit every time I include a ternary operator in a PR. He also insists on refactoring any block of code longer than two lines into its own function, even when it’s only used once.

    He is not well liked.

  • Kogasa@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    People ITT hating on null coalescing operators need to touch grass. Null coalescing and null conditional (string?.Trim()) are immensely useful and quite readable. One only has to be remotely conscious of edge cases where they can impair readability, which is true of every syntax feature

    • ferralcat@monyet.cc
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      Languages with null in them at all anymore just irk me. It’s 2023. Why are we still giving ourselves footguns.

          • Feathercrown@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            9 months ago

            Oh yeah I forgot, first you have to make a blog post, then a devlog, then review the top 10 best features of JS es6 (9 years after it was released…). Then shitpost on social media network for the other half of the week, and boom! You’re officially a Master Programmer!

    • KairuByte@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      I’m confused on how this is difficult to understand. Put aside the fact that it’s just a regular operator that… I mean virtually everyone should know, how hard is it to google “what does ?? mean in [language]” which has the added benefit of learning a new operator that can clean up your code?

      • DonnerWolfBach@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        11 months ago

        Well yeah but imagine you had to do that on most lines of the code? It would become very distracting imho. If you are in a team with people that have a lot experience and or will learn more anyway this is fine. But if you are in a team with not very good programmers which “will never learn” because they have other stuff to do, you should be careful when using code like this. Though I would prefer in the former of course.

        • KairuByte@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          11 months ago

          Honestly, and I mean this sincerely, if you’re on a team where the nullable coalesce is going to be confusing after the first handful of times encountered… look for a new job. It doesn’t bode well for their ability to do their jobs.

          This is like the guy at Walmart who needs hand holding each time they clean a machine, it’s a problem waiting to happen.