Three Essential Languages of the Modern Network Engineer
Culture change. Identity change. These are terms that have been used during and after NAF’s Autocon 0 to describe the transformation needed in network engineering.
I’m proposing language change to the list. But not in the way you might think. In short, my thesis is that modern network engineers must become proficient if not fluent within three different language families to help them achieve and exceed automation success.
Language 1: CLI
Yes, CLI. I don’t foresee a world anytime soon when network engineers won’t need to do some typey-typey “finger-driven networking.” Especially in brown-field networks, which comprise the majority of all networks. Based on all the talks I’ve heard since forever, including AutoCon, I don’t think this is a wild theory.
That said, everyone agrees that CLI shouldn’t monopolize the network engineering work day. But just like in the automotive world, until every car is a computer with wheels, you gotta sometimes pop the hood and use your hands. CLI seems like it will be part of life for a while.
Language 2: Code
This the no-duh part of this post. Whatever languages and related tools you or your team choose, code-based and automation-oriented communications with network machinery is the core skill of the modern network engineer. Embracing this requires overcoming the resistance to identity change that Chris Grundemann addressed in his recent NAF blog.
Language 3: Biz
As was emphasized multiple times at AutoCon, if you want succeed with automation in a business setting, you have to get the business on board. So you have to develop some fluency with business phraseology as a result.
You know what I mean. Service definitions and delivery. Internal or external customer solutions and benefits. Business cases and business justifications. Investments and returns (ROI). Elevator pitches, the “so what” and yada yada.
There’s a caveat. Not everybody in a team, but at least one or two people do need this skill. That said, every network engineer would be well served to pick this communication skill up for career progression.
Let me know what you think!
I write about startups, startup marketing, and some techie stuff (especially networking-related right now). You can see my posts and follow me on LinkedIn.
