I wish this wasn’t so true.
Just chilling
I wish this wasn’t so true.
It’s cool, it’s probably just self extracting. For convenience!
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.
LMAO we really have Lemmy cliques?
If it’s the Monopoly Man then it works on two levels. As one of the most popular games of all time, it’s safe to say it’s a big game. So the hunter would be a big game. And also hunting a big game.
BRB stealing your elementary school identity
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.
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.
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.
Anything to the zeroth power is 1. Quick maths.
At least you know better than socks with sandals!
If you’re color blind enough, this could be either!
Wait you’re telling me it’s not because they have a Kubernetes product?
Those aren’t buns any more. Pretty sure they’re labia.
Can we joke about log4shell? Maybe heartbleed?
Sometimes it’s not about GDPR and more about “we get no benefits from this area because we have no presence there but we get plenty of DDOS.” Source: had to do this at my $DAYJOB.
No, but they might easily run out of time to help one student understand if the rest of the 25 kids in the class are ready to move on.
If it makes the people paying taxes feel happy then I don’t see why not.