(☞゚ヮ゚)☞
(☞゚ヮ゚)☞
They’ll probably charge you for it.
Oh FFS. This timeline sucks.
Wait…. Wasn’t his brother the mayor? The dead one?
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.
Using Fastmail
In case those features are important to you
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?”
Don’t have to go back that far.
Luckily they had lizards in stock.
Everyone has a test environment. If you’re lucky you have a production environment too.
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?
Fibonacci indentation of course.
Why not git clean -dxf
?
I read the lint part and my brain forgot about everything else. You could stick the danger call in a pre commit hook though.
The one from science memes a few days ago