The one thing that really sticks out is the chin.

I see what you did there

Yeah, but by putting up the “we don’t support this” banner, they won’t have to deal with the complaints in the first place.

It’s also possible they want people to use Chromium for telemetry or other data-collection reasons, not sure.

Sort of. I imagine the idea is they only need to test on Chromium-based browsers.

Even using bullet points can help a lot in these situations (I use them quite often in emails with non-technical recipients).

It stops whatever is playing and starts playing the Rocky Horror Picture Show.

They’ve never had the best track record. The (first?) one on SNES was hot garbage, not sure if there was (an official) one before that. Your trepidation is warranted.

Hmmm… I predict something around a moderately-obscure but likeable celebrity.

And the lottery numbers will be…

4

• beans
• stroganoff
• jeans
• trout

As was foretold.

You have selected: POWER DRIVE

Maybe we’ll get a sequel to Lee Carvalo’s Putting Challenge II.

Damn, Louisiana got a whole fleet of orphan crushing machines.

There’s a reason they restrict these things. Trying to get around them is a bad idea. If you get caught, your professional life is over.

If you’re that desperate, bring a non-office laptop and use a hotspot on your phone.

This isn’t a sharpshooter fallacy–that would mean the good things OP is noting are made “good” after they happen.

If you think this is an unfounded optimism because there are a lot more bad things (or that things have gotten worse over the last two centuries), there’s an argument to be had there, but this isn’t it.

While there are lots of programming courses out there, not many of them will explicitly teach you about good programming principles. Here are a couple things off the top of my head:

• High cohesion, low coupling. That is, when you divide up code into functions and classes, try to minimize the number of things going between those functions (if your functions regularly have 6+ arguments, that’s a red flag and should be reviewed). And when something needs to be broken up into pieces, try to find the spots where there are minimal points of contact.

• Try to divide code between functions and files in a way that doesn’t feel too busy. If there are a bunch of related functions that are cluttering up one file, or that are referenced from multiple places, consider making a module for those. If you’re not sure what “too busy” means…

• Read a style guide. There are lots of things that will help you clean up and organize your code. The guide won’t necessarily tell you why to do each thing, but it’s a great tool when you don’t have another point of reference.

If you have a chance to take a “Software Engineering 101” class, this is where you’d learn most of the basic principles for writing better code.

If you’re already really comfortable with C, you could consider Java instead of Kotlin. The syntax is more similar, but Java doesn’t have as many features built into the language (and I imagine it’ll eventually be phased out anyways). You could try a sample project in each and see which one you prefer.

Somewhere, a somolier just vomited for no apparent reason.

At first glance, I assumed this was in c/shitpost and the laptop was jean-textured.

In BG 1 and 2, he actually has a rage ability similar to barbarians. I usually respec him as a barb in those games.

That makes sense–I figured Atari would be a generation behind NES, but I hadn’t considered single-game machines as a distinct thing. Thanks!

Is there a definitive authority on the generation numbers? I’d have classified the N64 as third generation.