I looked her up. I’m pretty sure this is satire judging from the comedic nature of most of her posts.

That sounds like a great question for the highest court in the country. Wait a minute…

Oh man, they’d be super offended by your comment if they could afford Internet. And read.

Elon musk surprised shareholders with this HOT investment trick.

United States be like: 👨‍🦯

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.

Maybe they’re on Azure.

If it disproportionately affected non-white or poor people.

Of course I avoid him. He’s me!

Law and order is a euphemism for free minority labor. Build the laws to keep jails full since those lameo historical killjoys made outright slavery illegal.

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

Plus you have plenty of time to tumble once or twice while your large codebase compiles.

There were 12 of these angry dogs, though. Not one trusting dog in a cinder pit. I don’t know if Noem would have been able to handle it even with a gun.

Yeah, this is pretty textbook selection bias.

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.

The other related advantage is being able to update data about a given B once, instead of everywhere it occurs as a child in A.

Do hot dogs need genders?

Well, when you’re a star, they let you do it. You can do anything.

Art

Is it really that surprising though?