Why certifications make me grouchy
While I support certifications, they also make me grouchy. Sometimes they make me really, really, grouchy, in fact — probably more grouchy than I have a right to be. You’ve probably heard the complaints a number of times.
For instance, there’s the problem of paper tigers, people who gain the certification but don’t have any real experience with the technology, or don’t really understand the technology. Paper tigers are bad, of course, but they’re generally easy to detect through a rigorous interview. In fact, paper tigers exist without the certification; it’s entirely possible for a solid resume to lead to a candidate that doesn’t have the skills advertised. Degree’s don’t really prove much, either, and it takes four years to get one of those (in theory), so I don’t know how much whining about this problem — as real as it is — is going to help.
Tony Li had a counter to this — he used to sit with a candidate’s resume in hand asking questions, and lining through skills he didn’t think the candidate actually had. At the end of the interview, he would hand the resume back to the candidate and say, essentially, “there, I fixed it Continue reading
Worth Reading: Networking with Fish
If anyone ever asks me why I write, or why I work so hard to draw other people into the larger networking world, I’ll point them to this post. One of the biggest goals of my life is to help people learn and grow. I’ll never become a millionaire in the process, but I’ll have a million friends, and that’s infinitely more important in the long run.
The post Worth Reading: Networking with Fish appeared first on 'net work.
Reaction: SD-WAN and Multiple Metrics
Ivan has posted a reaction to Ethan, which prompts me to… Okay, let’s start at the beginning. Ethan wrote a nice post on SD-WAN and the “shortest path we always wanted,” covering some of the positive and negative aspects of software defined WAN.
Ivan responded with this post, in which he says several interesting things, prompting some thoughts from yours truly…
Routing in SD-WAN environment is almost trivial…
Depends on what you mean when you say “routing…” If routing here means the discovery of the topology, and computing a best path through a topology, then controller based (centralized) “routing” is almost certainly more complex than distributed routing protocols. If routing here means, “take into consideration a wide swath of policies, including which link is most loaded right now, which link has the shortest queues, and lots of other things, and compute me a best path,” then a controller based centralized system is most likely going to be less complex. Take a gander through my last set of NANOG slides if you want to see where my thinking lies in this area — or read my new book on network complexity if you want a longer explanation.
The question is — Continue reading
Worth Reading: Currency and the Cloud
The post Worth Reading: Currency and the Cloud appeared first on 'net work.
Rule 11 Redux
Is it just me, or did we used to call this a mainframe?
The post Rule 11 Redux appeared first on 'net work.
The Tinker and the Geek: Information Technology
Imagine you’ve just woken up and found yourself in a small kingdom someplace in Europe around 1200 AD. You wander outside, interested in your surroundings, and find yourself in the middle of a fair. Taking stock, you see a man standing in a tent across the way who appears to be tapping on something with a small hammer. Working your way to the tent, you find he is actually tapping out intricate patterns on a small silver disc. While you’re not certain what the disc is for, you take a moment to ask — as any geek would — “are you in the information technology business?”
The tinker, living in 1200 AD, probably doesn’t even understand the question. “What’s information technology?,” he might ask. But let’s consider the tinker’s business. What does a tinker really do?
He takes some material, combines it with technical knowhow, including the development and use of tools, to create a product he knows customers will want. He can’t just use any old tool, or any old technique — he must know something about the correct technology to apply to the problem at hand. And he can’t just hammer anything out on the little Continue reading
Reading
"Reading takes a long time, though, don’t you find? It takes such a long time to get from, say, page twenty-one to page thirty. I mean, first you’ve got page twenty-three, then page twenty-five, then page twenty-seven, then page twenty-nine, not to mention the even numbers. Then page thirty. Then you’ve got page thirty-one and page thirty-three — there’s no end to it. Luckily Animal Farm isn’t that long a novel. But novels . . . they’re all long, aren’t they. I mean, they’re all so long.
" Martin Amis, Money —
Worth Reading: Why Hardware Still Matters
The post Worth Reading: Why Hardware Still Matters appeared first on 'net work.
The Pie Problem: Growth and Ratios
Why does it seem life goes faster as you get older? There are several reasons, of course — a primary one being it always seems there’s more you need to do and less you want to do, as you get older and take on responsibilities. I know that the last 17 years, since my first child was born, has often felt like a runaway train. But there’s another reason — a set of problems I’ve been working on with my younger daughter a lot because the math is easy, but the concept is hard.
It’s all in the ratios. To give an example, a teacher I once spent a lot of time listening to would often pose this to his friends:
You’re around 50. That means you’ve been given 2600 weekends so far, and you have about 1500 weekends left (give or take). What did you do with the weekends you’ve already lived, and what do you plan on doing with the 1500 you have left?
The math is simple — what’s the average life expectancy, how many weekends are there in a year, etc. But the problem is really all about ratios. The older you get, the less percentage Continue reading
IT/IT: Network scale is more than size
“Judge me by my size, do you?”
I’ve had several discussions with people over the years about the concept of scale in the world of network engineering. Most often, when network engineers think of a “large scale network,” they used to mention large service providers. Now they tend to think of some large cloud provider. But is scale really about size? I’m not much into the backflipping Yoda of the later Star Wars movies, but I would argue scale is much more about backflips than it is about being big.
So what is scale about? In the networking world, scale can be given the shorthand services x size. Standing in a huge data center with rows and rows of racks and blinking lights, it’s easy to forget about the services part of that equation.
A useful way to understand this is consider the services offered by a pair of networks, one large, and one small. The typical cloud provider’s network might contain thousands of nodes in a single data center — something more than 1000x10g (or 10,000x1g) ports on the edge is moderately sized in this world. What services does such a network — within the network itself — Continue reading