Vim koans

An old Unix master came to Master Wq. “I am troubled, Wq. You teach the way of Vim. vi is holy but Vim is not; its code sprawls, its features crowd memory; its binaries are vast, its behavior inconsistent. This is not the way of Unix. I fear you mislead your students. What can be done?”

Master Wq nodded. “You are right,” he said. “Vim is broken. Let us fix it. Shall we begin?”

Tom Ryder from, http://blog.sanctum.geek.nz/vim-koans/

slip:4ugevi1.

ɕ

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.)

 

ɕ

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, http://networkingnerd.net/2013/05/09/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!

ɕ

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, https://medium.com/future-tech-future-market/7b1a7ddb6ffe

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, http://www.marco.org/2013/03/19/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.

http://malwaremustdie.blogspot.com/2013/03/the-evil-came-back-darkleechs-apache.html

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?)

ɕ

NSA geekery

Let’s fix that shit and go get beers!

This. Yea verily this!

Here’s what I do know. There are plenty of frustrated system administrators, developers, engineers, “devops” and everything under the sun who don’t want much. All they really want is for shit to work. When shit breaks, they want to be notified. They want pretty graphs. They want to see business metrics along side operational ones. They want to have a 52-inch monitor in the office that everyone can look at and say: See that red dot? That’s bad. Here’s what was going on when we got that red dot. Let’s fix that shit and go get beers.

~ From, http://lusislog.blogspot.co.uk/2011/06/why-monitoring-sucks.html

slip:4ucowy3.

Hat tip to John E. Vincent. …and what’s network and systems administration (NSA)?

ɕ

The Customer Is The Product

I have yet to speak to anyone in the big blue room, (that is to say, anyone who does not work deeply within the Internet behind the magic curtain,) who has the slightest idea what is going on in general with “big data”, or specifically with “the customer is the product.” But “We Value Your Opinion” by Neven Mrgan — and that’s not a typo — is pure, sweet, ambrosia. It explains perfectly what is really going on. If you’re not paying for it, then you are the product. Have a cigar. Welcome to the machine. For more enjoyment and greater efficiency, consumption is being standardized.

ɕ