You can grow lots of fruit or veggies into a mold. I’m guessing that’s what this is. Not enough toes to be AI.

I wish this wasn’t so true.

Better yet you can configure gitignore globally for git. I do this mostly to avoid polluting repo ignore files with my editor specific junk but *.key and similar can help prevent accidents.

https://git-scm.com/docs/gitignore

Right, but AI is not the only way they’re doing the data collection.

Linux ISOs obviously

Air resistance is an outside force though. And pretty significant at road speeds.

That’s exactly what Half Life 3 will be.

This is true but it’s much easier to understand in retrospect unless you have a very very gifted math teacher (or series of teachers really) when you start learning it. For most people learning algebra it’s just another checkbox to tick for some reason. Plus pesky word problems that make you figure out the equations on top of that.

Now that I’m an adult I recognize what all of this was trying to teach me. But back in my school days it was just another thing I had to do between hanging out with friends.

I microwaved my phone and the battery level hasn’t gone down at all since.

BRB stealing your elementary school identity

Unprecedented only means there’s no precedent. This just hasn’t happened before at this scale.

Of course I avoid him. He’s me!

Samsung will add extra AI so their next ad will be employees being crushed into single device.

You don’t get them for free here. You have to purchase the Big Mac meal to get the complimentary gun.

Is there a language that anyone would say really does fare well for continued development or is it just that few people enjoy maintaining code? I’ve maintained some pretty old Go programs I wrote and didn’t mind it at all. I’ve inherited some brand new ones and wanted to rage quit immediately. I’ve also hated my own code too, so it’s not just whether or not I wrote it.

I have found maintainability is vastly more about the abstractions and architecture (modules and cohesive design etc) chosen than it is about the language.

Nonsense! We will write that history so that we’re clearly the good guys!

Unless you’re saying it’s possible we’ve not always been the good guys but surely that’s not it.

The real primary benefit of storing your relationships in a separate place is that it becomes a point of entry for scans or alterations instead of scanning all entries of one of the larger entity types. For example, “how many users have favorited movie X” is a query on one smaller table (and likely much better optimized on modern processor architectures) vs across all favorites of all users. And “movie x2 is deleted so let’s remove all references to it” is again a single table to alter.

Another benefit regardless of language is normalization. You can keep your entities distinct, and can operate on only one of either. This matters a lot more the more relationships you have between instances of both entities. You could get away with your json array containing IDs of movies rather than storing the joins separately, but that still loses for efficiency when compared to a third relationship table.

The biggest win for design is normalization. Store entities separately and updates or scans will require significantly less rewriting. And there are degrees of it, each with benefits and trade-offs.

Judging by the stars I’m pretty sure it was night time.

I think the joke is that the AI trained on SO data to the point that duplicate, similar, or common questions would get this treatment. Since that’s common enough on SO to be a meme.

Chilling with bears, if I understand recent events correctly.