this post was submitted on 26 Jul 2026
29 points (70.4% liked)

Technology

86679 readers
2701 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
29
Name before type: why 'age int' is better than 'int age' (benhoyt.com)
submitted 3 days ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world
61 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] elephantium@lemmy.world 1 points 8 hours ago (1 children)

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!
[โ€“] MangoCats@feddit.it 1 points 6 hours ago

adding a preprocessor directive

Yeah, I've had to do that a few times lately. Really tweaked me when gcc transitioned things from warnings to errors.

Migrating from 4.6 to .NET Core.

Are we on .NET 7? No, only 8 is available here without unreasonable effort to backdate. Does the .NET 7 code run in 8 without mods? Yes, but that doesn't change the hassle of talking endlessly about it.