Archive

Category Archives for "Russ White"

Looking Back, Looking Forward

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—

  • Read 58 Books (15333 pages)
  • 115,739 blog visits (according to WordPress)
  • Wrote 110,000 words for blogs, technical papers, etc.
  • Wrote 25,000 words for PhD seminars, etc.
  • Created 850 slides
  • Recorded 14 hours of videos/webinars

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

Exaggerating the End of NetEng

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