Changes In The Role Of Network Engineers.

The rise of software-defined networking, network automation, and DevOps has sparked much speculation about the future of network engineers and how their jobs will change. Interop 2016 provided some insights into the future role of network engineering and what they should focus on to move forward.

In a session with the provocative title "The network revolution is a lie," network software developer , SDN and network automation as a shock to the network industry, the result of which was a network professional. It was not, it was a simple tool to manage your network more efficiently.

"We wanted to be able to do this in a way that could be controlled by open platforms and APIs. Instead of introducing product and platform wars and never asking. He said a lesser-known revolution is happening in the networks, which is more about people than technology. "We rely too heavily on the technology side of this equation. We try to use technology to solve people and solve problems."

To that end, organizations need to invest more in people by educating them on what they can do to drive their business forward and "empowering them to become builders if they choose. He gave basic training, such as understanding what algorithms are and how Linux works.

"It is not an academic exercise. These bases are below some of the technologies we touch on," he added. "When we focus on the fundamentals, we are all really smart people. Investing on time can take a big leap in your career."

At the same time, he advised not to discount the SDN, or to think that open networks are only for giant internet companies like Facebook and Google. Oswald also said that his intention was not to beat network marketers. He sees them begin to implement better APIs in their technology and offer tools that are not linked to a large proprietary platform. He said that the API must be well documented to be effective.

Oswalt believes that there is plenty of room for networking between developers and non-developers, and for the audience of network professionals, "no one tells me I'm a software developer. Writing a Python script is no longer a network engineer.

He suggested writing a Python script that automates the more detailed part of the job. This gives network professionals better control over their infrastructure.

According to Oswald, running Linux on the switch is only for Google's big data centers, and open source code is perceived as less stable than proprietary platforms. "We need to learn to take advantage of open source instead of being afraid of it. We need more testing. We need more work. We need to spend our time, but getting control. It can do it."

Generalist's Return

Earlier in the day, senior Network Engineer Wilmarell led a session for an equally provocative title, The Death of a Network Specialist. He explained that it does not mean that there is no place for professionals. In fact, there is always a place for network professionals, especially in areas like wireless connection.

But he sees change happening where disciplines have extensive knowledge in various areas of IT. He said the IT department that has been isolated over the years is changing as new technologies like SDN, virtualization and cloud streamline IT management and reduce resource needs.

"The fundamental change is how we focus on being engineers. There is a new and fundamental thing called learning. "We need to change our mindset. Sometimes doing the same can be tricky ... we need to rethink how IT is organized and our role in it.

He predicted that the future would bring deep levels of specialization in multiple disciplines.

In addition to routing and switching, the skills that network engineers must focus on include security, systems, storage, and programming.