
Author Archives: Russ
Author Archives: Russ
The post Worth Reading: The Wandera Report appeared first on 'net work.
From time to time, folks ask me about how I write so much, or rather “how do you get so much done???” The reality is I tend to be very focused on tools and process. As I just revisited my tools over the new year, particularly when looking at a lot of new material that needs to be written, I thought it might be helpful to someone, perhaps, to write a post about what I’m using as the year turns over. Right now, I use—
I know I’m “old fashioned” in this tool set; I don’t do fancy markdown, markup, marksideways, or any of that stuff. I don’t swear by a platform (I don’t have a dog in the the Apple versus Microsoft fight), etc. But this set of tools has been modified, thought, and rethought across the last 20 years and the writing of millions of words of text contained in hundreds of papers, 11 books, many hours of classroom time, etc. I have been through periods when I really focused on finding some cool new tool to write with, maybe trying to “get rid of distractions,” or whatever else. Continue reading
The post Worth Reading: Smile vector appeared first on 'net work.
The post Worth Reading: Monitoring in containers appeared first on 'net work.
On this, the first “real” post of 2017, I thought it would be useful to reflect on the year that has passed, and consider the year that is coming. First off, 2016 in numbers—
These are all conservative numbers for the most part… I’ve not included journal and blog reading, nor have I tried to accurately count my writing output, as I often find it more frustrating than worthwhile. In the coming year, I plan to finish a book with Pearson, record at least one more video series (potentially more), and continue apace with blogging and other writing.
In 2016, I think we started to see the future of the networking market actually take shape. There seem to be three prongs developing; either companies will move their processing to the cloud, they will move to more hyperconverged/vertical solutions (essentially outsourcing design and architecture to vendors and consulting firms), or move to disaggregation. The day of the router as an appliance is done; we are moving to Continue reading
The post Worth Reading: Getting started with coding appeared first on 'net work.
‘net Work will be shut down next week so I can take a breather, spend some time with family, and get some of my todo list done…
The post Merry Christmas! appeared first on 'net work.
The post Worth Reading: Leaving it to the last second appeared first on 'net work.
The post Worth Reading: The year of silicon photonics appeared first on 'net work.
The post Worth Reading: The coming era of edge computing appeared first on 'net work.
The post Worth Reading: Driverless infrastructure appeared first on 'net work.
The post Worth Reading: The spillover effect appeared first on 'net work.
The post Worth Reading: Information paralysis appeared first on 'net work.
The post Worth Reading: Ransom by spreading the infection appeared first on 'net work.
The post Worth Reading: The canary appeared first on 'net work.
The argument around learning to code, it seems, always runs something like this:
We don’t need network engineers any longer, or we won’t in five years. Everything is going to be automated. All we’ll really need is coders who can write a python script to make it all work. Forget those expert level certifications. Just go to a coding boot camp, or get a good solid degree in coding, and you’ll be set for the rest of your life!
It certainly seems plausible on the surface. The market is pretty clearly splitting into definite camps—cloud, disaggregated, and hyperconverged—and this split is certainly going to drive a lot of change in what network engineers do every day. But is this idea of abandoning network engineering skills and replacing them wholesale with coding skills really viable?
To think this question through, it’s best to start with another one. Assume everyone in the world decides to become a coder tomorrow. Every automotive engineer and mechanic, every civil engineer and architect, every chef, and every grocer moves into coding. The question that should rise just at this moment is: what is it that’s being coded? Back end coders code database systems and business logic. Continue reading