Business continuity plan testing day.

Maybe it’s simply because he’s not the sitting president and his detail is much smaller? I’m not at all familiar with the way FPOTUS security is run but I do believe I remember they don’t get anywhere near the resources POTUS gets. They’re also not often running for reelection so this seems like an increased risk, reduced resources situation.

Yeah I’m not going to let the English language be shaped or solidified by people who have dedicated their lives to studying and deeply understanding language!

Is that a threat?

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?

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.

At least you know better than socks with sandals!

If you’re color blind enough, this could be either!

Can we joke about log4shell? Maybe heartbleed?

A few days of my pain in exchange for months of glory and beyond.

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.

I’m pretty sure they blame the others for not being more careful and that they if only they slipped and fell more often it wouldn’t hurt so much.