elephantium

Conway, is that you?

Spooky

Sigh, I was trying to set you up for a line like "yes, and I want them to NEED IT!"

Even for Nazis?

Maybe you should have proofread your comment before posting a grammar gotcha!

I'm really starting to hate this technique in making titles. Tf does the age of the particular loophole they used matter? It implies that the problem is in using rules that have been around for more than 5 minutes rather than in the action of circumventing the rights of the citizens.

Meanwhile I'm playing Oxygen Not Included, and like half the time I look something up about the game, half the results are on reddit. There's a lot of accumulated stuff on there that's still helpful.

Of course, any false or outdated info will quickly be obvious when you start up the game again. Lower stakes than soldering safety.

This split shows up in interviews, even for senior-level positions. It's infuriating. Want to get hired? Memorize the right snippets from the documentation!

Want to do the job? Be able to find what's helpful in the docs and incorporate it into what you're trying to do.

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.

So true! It's been a while since I've read any of his stuff. The last book of his that I read was The City & the City. Weird and fun and interesting all wrapped up together.

The 1999 cinematic masterpiece starring Rachel Weisz and Brendan Fraser?

Good flick.

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!