Worth Reading: More Leaky Routes
The post Worth Reading: More Leaky Routes appeared first on 'net work.
Consequences Teach
"The sad consequences of cruelty, injustice, violence, deceit, and laziness teach us to be gentle, just, moderate, faithful, and industrious. The experience is lengthy, but it is efficient.
" Raoul Audouin — http://ProvidenceandLiberty
The post Consequences Teach appeared first on 'net work.
Worth Reading: Don’t be so Surprised
The post Worth Reading: Don’t be so Surprised appeared first on 'net work.
Worth Reading: Politics and Technology
[P]re-acting to something that hasn’t happened yet is nonsense.
Refusing to learn from people you don’t agree with isn’t a particularly modern vice, but in our world of information overload, where there are so many voices that we can choose to listen only to people we agree with, it does create a particularly modern narrowness of mind.
The post Worth Reading: Politics and Technology appeared first on 'net work.
Why I Support Certifications
I’m betting that I could take my certifications off my resume and still have a fair chance at finding a job. It’s a guess, of course, and I’ve never tried any sort of an experiment towards finding out, but the point is this: at some point in your career, certifications should become just one more thing on an excellent resume, rather than the focal point of your resume. Given this, why do I still support certifications? To answer this question, I need to back up into the certification development process a bit.
One of the strangest “mind trips” I’ve ever encountered was working with the “psycho’s” (psychometricians, really, but you know how engineers are with long words) through the entire CCDE/CCAr process. The two things we were challenged constantly were:
- What does the minimally qualified candidate look like?
- How do you intend to test for that skill?
Both of these are hard questions.
The first question we turned into a simpler one (again, you know how engineers are): Why do I care? When someone would suggest a particular question or skill, they were immediately met with the counter — Do I care? If I were a designer working on a Continue reading
Worth Reading 06:19
Much as I’ve been trying to keep up on interesting stuff to read on the right column, I still seem to have built a long list of bookmarks! Having nothing better to do on a Friday morning, I’m dumping them on your.
So there! 
I’ve posted in the past on the problems of the IT job market. Primarily I think it’s too much about “what narrow set of skills do you have,” rather than, “are you a good engineer,” and I think we engineers are as much to blame as anyone else for this. “Yeah, but do you know about the latest gobberfubble embedded fingernail pick API??” we say with pride, trying to find something we know about the person we’re interviewing does. Interviews shouldn’t be about making yourself feel better about your technical skill — they should be about finding a good engineer for your team. Okay, I’ve ranted long enough — it’s time for Infoworld to take over on this score with more practical advice.
The Midyear State of the IT Job Market.
By the way, I know my response to the esoteric game won’t work for everyone, but whenever someone gets me into this position of Continue reading
Anger
"I suppose that when one hears a tale of hideous cruelty anger is quite the wrong reaction, and merely wastes the energy that ought to go in a different direction: perhaps merely dulls the conscience which, if it were awake, would ask us, “Well, what are you doing about it? How much of your live have you spent in really combating this?”
" C.S. Lewis —
Review: Building Microservices
Building Microservices
Sam Newman
ISBN: 978-1-491-95035-7
Scale out where you can, scale up where you must.
Someone, somewhere, should probably start a collection of “where you can, where must” sayings, as these rules of thumb (thumbs were used by carpenters instead of a ruler to measure an inch, apparently) are important to remember, even if they’re imprecise. Route where you can, switch where you must — really refers to using layer 3 versus layer 2 networking as much as possible — for instance. Scaling out, from the perspective of network engineering, is all about repeatable modules, spine and leaf fabrics, and distribution of the control plane (didn’t think of that last one, did you?).
But what does scaling out mean in the application development world? It means splitting services into modular pieces which interact over the network. The ultimate goal of splitting services is to get to the microservice.
But what is a microservice?
To answer this question, you need to turn to the first chapter of Scaling Microservices, which says, “Microservices are small, autonomous services that work together.” Sam Newman, in the rest of the first chapter, explains the concept well, from a number of different angles, Continue reading
Worth Reading: SD-WAN and Per Application Routing
Of course, routing on a per application (or a per packet) basis provides more optimization, but it also adds more state in the control plane, and it increases the speed at which that state changes. In my forthcoming book on network complexity, I’m going to work around a model of state/speed/surface, with a side of optimization, to gain an understanding of network complexity and how to manage it.
The post Worth Reading: SD-WAN and Per Application Routing appeared first on 'net work.
Worth Reading: An Open Source Routing Lab
Worth Reading: An Open Source Routing Lab
I’ve been planning on setting this sort of thing up, as well, and blogging through it. Even though I was beat to the punch, it’s still on my todo list. And yes, I stupidly posted this with no link the first time. Blame it on my mind going in five different directions at once.
The post Worth Reading: An Open Source Routing Lab appeared first on 'net work.
Explain-a-holic (Communicate Clearly)
But just a couple of days ago, I was talking to someone about managing expectations in the IT world. How do you convince someone else to buy into a project? How do you get them to back your idea, rather than inventing their own? While the question itself is interesting, I’m going to leave my thoughts on it to another post.
What I realized, halfway through answering the question, was that I was sucking up a lot of time talking about things that probably didn’t matter. I was spending time talking about the problems of getting people to own the problem, or make them believe they’d invented the solution, and specific projects I’d been involved in where we could never convince a wide group of people to buy into our ideas and solutions.
At some point, I’m certain I sounded like this snippet from a recent email —
Like if I asked, “what is 1+1?” he might say, “one takes 1, and adds 1 to it, and you get the next integer, which is really quite interesting, because you can do this over and over again, and never get the same answer, which is a bit like…”
There are, Continue reading
Segment Routing
Segment routing could change the way MPLS networks function and facilitate the adoption of SDN.
The post Segment Routing appeared first on 'net work.