Monday, August 24, 2020

Network engineers don't have to become programmers

 In the face of the turmoil of the evolution of network technologies, engineers trained in this area should not rush to learn a programming language. But to compete in the new world of software-defined networks, it may be more important to start thinking like a programmer.

The idea emerged reinforced this week in a debate by the Open Networking User Group and generating a favorable response from the audience. The days of managing individual switches and routers, configuring them with command-line interfaces (CLI), proprietary tend to end, said the four panelists at the organization's Spring conference in San Francisco, during the last week.

Although Software Defined Networks technologies have not entered every company, new approaches to enterprise IT and the availability of public clouds lead organizations towards the use of more agile and automated networks, they confirm. Internal network management teams will need to match the speed of evolution of cloud providers in tasks such as creating new virtual machines, warns Stanford University professor David Cheriton.

"At one point, the CIO will ask, 'Why does it cost us so much it takes us much longer to do the same?'" Illustrates Cheriton. SDNs absorb many configuration tasks that some network engineers have spent their careers doing manually, raising concerns about the security of their jobs and how these technicians should evolve.

Freed from port and route configuration tasks, some network engineers are already taking on more sophisticated functions, such as designing better systems. With these changes, some network professionals will begin to code. But that doesn't mean writing software from scratch and starting your career as a programmer again.

network engineer description

No comments:

Post a Comment

Definition of RF Technician

Definition It involves the passage of a high frequency current through a cannula that is totally isolated except for the tip (2-4 mm) which ...