A variable's name is more important than its type, so the name should be more prominent and come first in declarations.
    • elephantium@lemmy.worldEnglish
      1·
      4 months ago

      Most of my version-upgrade woes seem comparatively recent, lol

      1. Nullable contexts. It’s “easy” to update this with a setting in your project file! … but it adds warnings to basically every file in the project :( You could break it up by adding a preprocessor directive, but it still added a lot of noise at the time.
      2. File-scoped namespaces. I like this feature for new code, but OUCH does it mess up code reviews when it’s an incidental change. I really grew to love Github’s “ignore whitespace” setting in the PR diff view because of this.
      3. Migrating from 4.6 to .NET Core. There were a few times when a deploy just … stopped. It worked on our desktops, and it worked on our test server, but the prod deploy just choked. We might have finally gotten a clue about what was wrong from the event viewer, but it’s been a while. I do recall that our usual troubleshooting path was useless in this case!
        • elephantium@lemmy.worldEnglish
          1·
          4 months ago

          Are we on .NET 7?

          No. We weren’t. This one was about a decade ago, around the time they first released .NET Core.

          talking endlessly about it

          Eh…ideally you’d have the conversation once, around what upgrade strategy to use, then execute on it. Upgrade yearly vs. ride out LTS windows. Etc.