I’m gonna guess the original version of this joke said “crashed” instead of “fell over”, cause then it would actually be ambiguous enough for the premise to work.

Time to find out if someone else has access, and can make a copy and send it to you, and then you can play dumb about where/how you got your copy.

Without his help, computer science would be wirth-less.

A view is a saved query that pretends it’s a table. It doesn’t actually store any data. So if you need to query 10 different tables, joining them together and filtering the results specific ways, a view would just be that saved query, so instead of “SELECT * FROM (a big mess of tables)” you can do “SELECT * FROM HandyView”

Somebody tell this dude about views.

Wasn’t there a study that found if you tell people you’re working on something, you get the same brain reward chemicals as if you actually did it and told everyone? So if you tell people before you’re done, you might just go “meh, I’m good, the rest sounds hard”. Or something like that.

What’s a ghost’s favorite data type? a BOOlean!

“The importance of URLs to articles.”

The author does a good job explaining how join diagrams are more accurate than venn diagrams, but by saying that venn diagrams are bad and wrong, I feel like they completely miss the point. The venn diagrams can be understood almost instantly, whereas the join diagrams take time and thought to take in.

If someone was brand new to sql joins, sure maybe I would say a join diagram is better for them, so they can really understand what is happening. But for someone who just wants a refresher on join types they rarely use, I think the venn diagrams win. I guess ultimately I don’t like the claim that one type of diagram is simply “better”.

I’ve also found that when you ask it to show someone “drawing a bow” they end up with a strange mix of a pencil that goes up to their cheek, and another weird stick going perpendicular to whatever they’re doing, and other weird bow-related artifacts. It’s pretty funny. (At least with SD 1.5)