UDP threeway handshake

On 05/07/13 09:15, Michael Tiernan wrote:
>  “What is the UDP three way handshake?” He said he was wondering how many people would catch the question’s trick.

You send three UDP packets in three different directions, then shake the hand of the person next to you.

Robert Lanning from, «https://lists.lopsa.org/pipermail/discuss/2013-May/018116.html»

ɕ


SOLID object-oriented design

Five basic principles of object-oriented design. Not the only five, but five which are, well, SOLID.

Single responsibility – A class should have only a single responsibility.

Open/closed – Open for extension; Closed to modification.

Liskov substitution – Objects can be replaced by instances of their sub-types without breakage or surprise.

Interface segregation – Many, specific interfaces – that is, APIs – are better than fewer, more general-purpose interfaces. (…or “interface” in the worst case.)

Dependency inversion – Depend upon the abstraction. (Not upon the specific concretion.)

 

ɕ


Web pioneers win inaugural $1.5 mn engineering prize

Web pioneers win inaugural $1.5 mn engineering prize

ɕ


Coffee as as Service (CaaS ?!)

I have a hard time keeping all the cloud terms straight. Everything seems to be available As A Service (aaS). Try as I might to explain them, it just didn’t click for some people. Since cloud terms are so nebulous some times, I decided I need to put everything in a context that people understand. Therefore, I present…Coffee as a Service (CaaS)

~ Tom Hollingsworth from, Coffee As A Service

slip:4uneco1.

This will now be my go-to way of explaining the _aaS buzzword bingo. “I wish I had a… Oh! A cup of coffee!” aka SaaS. Brilliant!

ɕ


Scheme Relative URLs

//example.com/img.png is a perfectly valid URI syntax as per RFC 3986: Section 4.2. It is relative to the current scheme, and … it can be very useful when switching between http and https, because you won’t need to explicitly specify the scheme.

~ Daniel Vassallo from, Network-Path Reference URI / Scheme relative URLs

How is it possible I’ve never learned this?

ɕ


Does free work?

If you don’t understand what all the hubbub is about Google Reader, RSS, free services… here are three bits to get you thinking:

The Customer Is the Product

What if someone invented a service where, instead of having to check all your important blogs, instead of having to check Twitter and Tumblr a million times a day, you could get all the updates in one place? Great idea!

~ Ryan Holiday from, Our Regressive Web

slip:4umefu1.

Free is so prevalent in our industry not because everyone’s irresponsible, but because it works. … In other industries, this is called predatory pricing, and many forms of it are illegal because they’re so destructive to healthy businesses and the welfare of an economy. But the tech industry is far less regulated, younger, and faster-moving than most industries. We celebrate our ability to do things that are illegal or economically infeasible in other markets with productive-sounding words like “disruption”.

~ Marco Arment from, Free works

slip:4umafe1.

ɕ


Swamp maintenance

It’s hard to maintain the Everglades for the tourists when you’re up to your ass in alligators.

Curious about what I do? Here’s a glimpse.

The Evil Came Back

slip:4ubote2.

(If you’ve understood any of that, you will be cursing the scum-of-the-earth people who spend time making up this malicious stuff. Awesome that! …let’s fix this sh*t and go get beers.)

Now, Imagine you were working on something when that little item was brought to your attention. “Hmmmm, I wonder if that’s as serious as it sounds . . . “

  1. You need to understand the threat; That’s rather difficult once you realize that the god-level security geeks haven’t fully figured it out yet.
  2. You have various systems that might be affected; You need to check them.
  3. If you’ve been attacked, is it safe to even check the systems? …ok, you’ve figured that out.
  4. Check them. All of them.
  5. Devise your defense, (or decide it doesn’t apply to you.)
  6. Now implement changes to fix, or prevent, future problems.
  7. Then wonder: Do my usual work practices and designs prevent this vulnerability? …should I change my practices or designs? …can I generalize this specific problem into a general sort of problem that I can defend against all future problems like this one?
  8. Great! Do that.

Then you can go back to being the mother hen roosting on her eggs.

I’m not complaining. This is simply a part of what I do. Just thought perhaps some of you, dear readers, might like a glimpse behind the curtain.

ɕ


RFC for HTTP 700-series errors

oh. my. god. https://github.com/joho/7XX-rfc

This is, hands down, the geekiest piece of humor I have ever seen. HT to @dmuth who now owes me a cup of coffee to replace the one I blew out my nose onto my keyboard.

If you, my dear reader, care to do the ‘what the hell?’ deep dive:

  1. What’s an HTTP header?
    (it’s the glue that makes all the interwebs parts work together)
  2. What are the actual HTTP response codes?
    (200 good, 404 bad, 759 – Unexpected T_PAAMAYIM_NEKUDOTAYIM !)
  3. What’s an RFC?
    (request for comments, i.e. “hey, uh, fellows, maybe we should do it this way…”)
  4. The HyperText Coffee Pot Control Protocol (HTCPCP/1.0)
    (ie, prior art in RFC humor. Please notice the honest-to-gawd IETF.org URL on that one kids. Yes, the IETF like kinda determines how the intertubes work, and they have absolutely THE ugliest website.)
  5. An obscure HTTP response code joke
    (you do know to read the “alt-texts” on XKCD cartoons, right?)

ɕ


Old Timey Internet Sounds

The nostalgic sound of dialup modems’ negotiations visually explained.

slip:4ubote3.

ɕ


vi registers

Advanced Vim registers

slip:4ugeaa1.

Suddenly, my paltry `dd` and `y` vi skills seem pathetic.

Note to self: Read this. Read it again. Repeat.

ɕ