Network Automation Engineer Persona: Part Two
This article is number two in a series. The first part can be found here.
There has been a thought trend in the last few years leading network engineers to think they need to be developers. This is totally nonsense. When we want to learn a new skill, there is a precursor which says “I want to do X, so therefore I need to learn about what X”. If you’re thinking “I should be learning Python”, I ask to what goal? What is making you ask this question? Maybe the question should be, for a network automation engineer role, what skills do I need to learn? Stop guessing!
The Network Automation Engineer role combines deep network knowledge, with the ability to describe, collect and transmit domain specific data through one or more abstraction layer type components. It requires knowledge of how to collect data from databases and data-stores of various types. Where does a list of IP addresses get stored? How are they stored? How are they retrieved? The role requires an awareness of the cause for making a change and the implication of making them. Gaining the skills to become this persona isn’t a full career change, but a Continue reading
Salesforce uses a low-code orchestration for its IoT software.
Is session-based signaling in the future for SDN and NFV architectures?
Three service providers are leading the initiative: DT, Telefonica, and NTT Docomo.
Thirty entities have so far participated in the equity funding round.
Intel mourns loss of former CEO; F5 recruits top exec from Oracle; Verizon's top media exec steps down amidst Yahoo failures.
The companies also plan to build a joint security product.