LMAO we really have Lemmy cliques?
Just chilling
LMAO we really have Lemmy cliques?
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.
Can we joke about log4shell? Maybe heartbleed?
Can this power be learned?
Yeah, the image (not mine, but the best I found quickly) kinda shows a rebase+merge as the third image. As the other commenter mentioned, the new commit in the second image is the merge commit that would include any conflict resolutions.
Merge takes two commits and smooshes them together at their current state, and may require one commit to reconcile changes. Rebase takes a whole branch and moves it, as if you started working on it from a more recent base commit, and will ask you to reconcile changes as it replays history.
This is floating point. We also need to know what happens when you escape with -0.
Fair point. There’s a fine line between programming and creating data that a program operates on. I tend to think writing text to produce nontext output is more programming than not.
But also, you’re making a computer do what you want, and something that it wasn’t programmed by the factory to display, when you write HTML. You’re programming.
That’s the final invisible panel. Code that definitely won’t compile, does compile, and tests all pass.
// see if the runtime notices
limit := limits[len(limits)]
Some people have tongue tie and might have a much harder time lifting their tongue, sometimes being completely impossible. It’s usually corrected in babies these days right around birth, but isn’t always and could definitely explain the confusion.
Wait till you hear what strings are under the hood. Integers in a trench coat!
I want to start keeping some bumper magnets in my car for the latter category. Like that guy who tossed them onto shopping cart abandoners. Really gets me grumpy when people just zip in without zippering.
There’s no one right way. Saying there are wrong ways doesn’t imply the existence of one right way, though.
I wish this wasn’t so true.