Or alternatively: > I would UDP joke tell you a… but you get it might not.
> I would UDP joke tell you a… but you get it might not.
21–30 of 55 posts
Or alternatively: > I would UDP joke tell you a… but you get it might not.
> I would UDP joke tell you a… but you get it might not.
"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?"
I knew about enough to fill an index card: enough for an adequate interview answer, but not enough that I would relish getting follow-up questions.
While deciding what to say I started with this joke. The interviewer laughed and moved on to the next question. I got the job offer.
I'd share my joke about HTTP here, but it makes me feel insecure.
There are two kinds of people when it comes to UDP.
Btw, it reminds me of "10 kinds of people, those who understand binary and those who don't"
Or alternatively: > I would UDP joke tell you a… but you get it might not.