And as a bonus the flows were never fully specc’d each time right?
And as a bonus the flows were never fully specc’d each time right?
If I get to learn something then that’s a bonus.
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.
X chromosomes are stored in the balls
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?”
“Build a man a fire, and he’ll be warm for a day. Set a man on fire, and he’ll be warm for the rest of his life.”
You can get a clock that is set up counter clockwise to mess with people
Planetary intergalactic.
How about playing games with programming instead…
deleted by creator
A broader perspective than tech bro would be nice though.
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/