easy-accordion-free domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114zoho-flow domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114I\u2019ve been involved with network engineering for the better part of 20 years now and I\u2019ve observed massive changes in the industry during those two\u2026 Read more on Cisco Blogs<\/a><\/p>\n \u200b[[{“value”:”<\/p>\n I\u2019ve been involved with network engineering for the better part of 20 years now and I\u2019ve observed massive changes in the industry during those two decades, from Frame Relay and ATM becoming obsolete to Ethernet taking over and becoming a pervasive technology. But besides me getting older and different transport technologies going through existential crises, the biggest development in all these years was the emergence of network automation and programmability. This is the change that has probably affected the most what it means to be a network engineer these days.<\/p>\n Yes, different technologies and protocols come and go in classical network engineering, but automation requires a completely new set of skills. These new skills vary in complexity and usability from learning how to write YAML files and working with Ansible, to writing HCL files for Terraform configuration, to being fully proficient in a programming language such as Python or Golang. The basis and foundation for all these new skills comes from software development. This has always been tangential to network engineering, but with the advent of automation is taking a front row seat.<\/p>\n Depending on the size of the networks and environments you are working on, and how your company is organized, it might be you that has to become a proficient software developer and bring automation into your organization. Or, you might have to work with software developers and explain to them how the network is running, what needs to be done to automate your business processes and workflows in a language and with concepts that they understand and that they can easily turn into source code.<\/p>\n If all of this sounds daunting to you, don\u2019t despair, you are not alone on your automation journey. We have a fantastic community of engineers at different stages in their careers that are more than happy to share their hard learned automation lessons with you. I host a weekly live stream on Wednesdays at 9:00AM PT called Simplifying Network Automation with NetGru<\/strong> that is being broadcast live and recorded on the Cisco DevNet YouTube channel<\/a>\u00a0and LinkedIn account<\/a>.<\/p>\n In two recent episodes I\u2019ve had the privilege of hosting Julio Gomez, Principal Sales Architect at Cisco. We\u2019ve discussed how applications have evolved over the years \u2013 from monoliths to micro services architectures, containerized applications and Docker, Kubernetes, CI\/CD pipelines, telepresence (not the Cisco one), mirrord, Okteto, and more. Most importantly, we talked about how to be a network engineer in this new world surrounded by all these exciting technologies. Here are links where you can watch these recorded episodes:<\/p>\n Watch the first episode<\/a> Simplifying Network Automation with NetGru<\/strong>Wednesdays at 9:00AM PT<\/em><\/strong> “}]]\u00a0\u00a0Here’s help for being a network engineer in the age of automation and programmability. Mark your calendars to tune in to the weekly live stream “Simplifying Network Automation with NetGru.” Wednesdays at 9:00AM PT.\u00a0\u00a0Read More<\/a>\u00a0Cisco Blogs\u00a0<\/p>","protected":false},"excerpt":{"rendered":" <\/p>\n I\u2019ve been involved with network engineering for the better part of 20 years now and I\u2019ve observed massive changes in the industry during those two\u2026 Read more on Cisco Blogs<\/a><\/p>\n \u200b[[{“value”:”<\/p>\n I\u2019ve been involved with network engineering for the better part of 20 years now and I\u2019ve observed massive changes in the industry during those two decades, from Frame Relay and ATM becoming obsolete to Ethernet taking over and becoming a pervasive technology. But besides me getting older and different transport technologies going through existential crises, the biggest development in all these years was the emergence of network automation and programmability. This is the change that has probably affected the most what it means to be a network engineer these days.<\/p>\n Yes, different technologies and protocols come and go in classical network engineering, but automation requires a completely new set of skills. These new skills vary in complexity and usability from learning how to write YAML files and working with Ansible, to writing HCL files for Terraform configuration, to being fully proficient in a programming language such as Python or Golang. The basis and foundation for all these new skills comes from software development. This has always been tangential to network engineering, but with the advent of automation is taking a front row seat.<\/p>\n Depending on the size of the networks and environments you are working on, and how your company is organized, it might be you that has to become a proficient software developer and bring automation into your organization. Or, you might have to work with software developers and explain to them how the network is running, what needs to be done to automate your business processes and workflows in a language and with concepts that they understand and that they can easily turn into source code.<\/p>\n If all of this sounds daunting to you, don\u2019t despair, you are not alone on your automation journey. We have a fantastic community of engineers at different stages in their careers that are more than happy to share their hard learned automation lessons with you. I host a weekly live stream on Wednesdays at 9:00AM PT called Simplifying Network Automation with NetGru<\/strong> that is being broadcast live and recorded on the Cisco DevNet YouTube channel<\/a>\u00a0and LinkedIn account<\/a>.<\/p>\n In two recent episodes I\u2019ve had the privilege of hosting Julio Gomez, Principal Sales Architect at Cisco. We\u2019ve discussed how applications have evolved over the years \u2013 from monoliths to micro services architectures, containerized applications and Docker, Kubernetes, CI\/CD pipelines, telepresence (not the Cisco one), mirrord, Okteto, and more. Most importantly, we talked about how to be a network engineer in this new world surrounded by all these exciting technologies. Here are links where you can watch these recorded episodes:<\/p>\n Watch the first episode<\/a> Simplifying Network Automation with NetGru<\/strong>Wednesdays at 9:00AM PT<\/em><\/strong>How to be a network engineer in the age of automation<\/h2>\n
You are not alone<\/h2>\n
\nWatch the second episode<\/a><\/p>\nMark your calendars to tune in to the weekly live stream<\/h2>\n
\nBroadcast live and recorded on the Cisco DevNet YouTube channel<\/a>\u00a0and LinkedIn<\/a><\/p>\nHow to be a network engineer in the age of automation<\/h2>\n
How to be a network engineer in the age of automation<\/h2>\n
You are not alone<\/h2>\n
\nWatch the second episode<\/a><\/p>\nMark your calendars to tune in to the weekly live stream<\/h2>\n
\nBroadcast live and recorded on the Cisco DevNet YouTube channel<\/a>\u00a0and LinkedIn<\/a><\/p>\n