The post Worth Reading: Security and the IoT appeared first on 'net work.
The post Worth Listening: Optical for the Campus appeared first on 'net work.
The post HL: The Art of Network Architecture appeared first on 'net work.
C.S. Lewis, Letters to an American Lady
The post Good Works appeared first on 'net work.
The Craft of Research
Booth, Colomb, and Williamns
Engineers don’t often think of themselves as researchers. After all, what does writing a bit of code, or building a network design, have to do with research? Isn’t research something academic type folks do when they’re writing really long, and really boring, papers that no-one ever reads? If that’s what you really think, then you’ve come to the wrong blog this week. In fact, I’d guess that a good many projects get off track, and a good number of engineering avenues aren’t explored, because people just don’t know how to — or don’t enjoy — research. Research is at the very heart of engineering.
Even if it’s never published, writing a research style paper can help you clarify and understand the issues you’re facing, and think through the options. Reading IETF drafts, software design specs, and many other documents engineers produce is depressing some times.
Can’t we do better? Of course we can. Read this book.
This book, while it does focus on the academic side of writing a research paper, is also a practical guide to how to think through the process of researching a project. The authors begin with a Continue reading
A note to remember — I don’t agree with everything I put up as a worth reading article. There are some good things here, and some bad. Watermelon seeds are meant to be spit out, though, not eaten with the sweet red stuff. And don’t even get into the rind.
The post Worth Reading; The Great Man Theory appeared first on 'net work.
The post Highlight: Why Your Presentations Stink appeared first on 'net work.
The post Worth Reading: Expert Versus Nonexpert appeared first on 'net work.
I guess I’m semi-famous. Or maybe I’m a moderately sized fish in a rather small bowl. Whatever the reason, a lot of people reach out to me for career advice. Which is okay, of course — I make it a personal policy to answer every email that’s addressed to me, individually, that I receive. It only takes a minute or two, after all, and it drives me nuts when I send an email to someone that seems to go into a black hole. I try not to be the person that drives me nuts.
So a couple of times a week, I open my inbox to find either an email or a message through some social network (the only social networks I actively use, by the way, are Twitter and LinkedIn, so if you friend me on Facebook, or send me an invite to something else, I’m not likely to accept) asking some variation of a couple of questions. The one I want to address in this post is probably the hardest to answer.
How can I become an architect/really good engineer/really good writer/really successful/etc.?
The snark inside me just wants to answer, “just change your title on LinkedIn, that’s Continue reading
The post Worth Reading: Access Control with Segmentation appeared first on 'net work.
This is a point that many people don’t get — if all businesses are data businesses (and they are, despite the constant refrain I’ve heard throughout my career that “we don’t make technology, here, so…”), then all the data, and all the analysis you do on that data, is just like the famous Coke recipe.
Know data, know your business. No data, no business.
It’s really that simple. When will we learn — and take this idea seriously? And when will we realize this rule applies to the network as well as the data in many cases?
The post Worth Reading: Outsourcing appeared first on 'net work.
As I learned in my early days in electronics, every wire is an antenna. This means that a signal in any wire, given enough power, can be transmitted, and that same signal, in an adjacent wire, can be received (and potentially decoded) through electromagnetic induction (Rule 3 may apply). This is a major problem in the carrying of signals through a wire, a phenomenon known as cross talk. How do communications engineers overcome this? By observing that a signal carried along parallel wires at opposite polarities will cancel each other out electromagnetically. The figure below might help out, if you’re not familiar with this.
This canceling effect of two waveforms traveling a pair of wires 180deg out of phase is why the twisted is in twisted pair, and why it’s so crucial not to unbundle too much wire when punching down a jack or connector. The more untwisted the wire there is, the less effective the canceling effect is around the punch down, and the more likely you are to have near end or far end crosstalk.
If you consider one row of memory in a chip one wire, and a second, adjacent row of memory in the Continue reading
The post Worth Reading: Learning from Chambers appeared first on 'net work.
The post Worth Reading: Commoditization of the Black Market appeared first on 'net work.
The post HL: What I learned by being laid off appeared first on 'net work.
Tom has an interesting post over at The Networking Nerd on one of my favorite areas of discussion — certifications. To give you a sense —
I think the problem exam writers face is the defensibility problem. The problem of defensibility has been so strongly pushed into my head, from my years working on the CCDE and CCAr, that I tend to apply the problem to just about everything I do any longer. To state the problem, within the certification space, as succinctly as possible —
If someone sues me because they failed this exam, what evidence can I bring forward to prove this specific person should not have passed the exam.
It’s actually not as easy of a question to answer as it might appear. Why is your cut score set to x? Continue reading
The post Worth Reading: The Uber Imperative appeared first on 'net work.