The one from science memes a few days ago

Be awkward by sharing a weird hyper specific fact

That one time cocoa pods (a dependency management system for iOS development) was essentially doing a DDNS when their spec repo was using GitHub as a CDN. https://blog.cocoapods.org/Master-Spec-Repo-Rate-Limiting-Post-Mortem/

And as a bonus the flows were never fully specc’d each time right?

It’s hilarious when the identified problems come back around to bite the organization, when the priorities have been to work on poorly specc’d features instead.

Hello, would you like to hear a TCP joke?

Edit: since no one is biting here’s the full joke

“Hi, I’d like to hear a TCP joke.”
“Hello, would you like to hear a TCP joke?”
“Yes, I’d like to hear a TCP joke.”
“Ok, I’ll tell you a TCP joke.”
“Ok, I will hear a TCP joke.”
“Are you ready to hear a TCP joke?”
“Yes, I am ready to hear a TCP joke.”
“Ok, I am about to send the TCP joke. It will last 10 seconds, it has two characters, it does not have a setting, it ends with a punchline.”
“Ok, I am ready to get your TCP joke that will last 10 seconds, has two characters, does not have an explicit setting, and ends with a punchline.”
“I’m sorry, your connection has timed out. Hello, would you like to hear a TCP joke?”

Have you seen what they’re leaving us? No thanks.

Luckily they had lizards in stock.

The malicious compliance that is needed.

I only glossed over it… but this looks like it’s trying to check dynamic typing issues? It’s like a statically typed language with extra steps?

Banana curry pizza is popular in Sweden.

If you ever want to bullshit a junior, use the git man page generator

Jellyfin and jiggle

Was not expecting to keep watching but damn yeah the work that went into this is top tier.

=== is just == with extra steps