CCNA or Python? | Should I Become a Network Engineer or a Programmer?

About this video

NetworkChuck answers ‘CCNA or Python?’ by rejecting the either/or choice. He argues the CCNA is still extremely valuable and tells viewers not to be discouraged by claims it is worthless, crediting Cisco certifications with building his own career, while also arguing programming is the future of networking: software-defined networking, programmability and intent-based networking mean individually configuring switches and routers in the CLI will decline in favour of controllers, scripting and automation — though engineers must still understand the underlying configuration. The core of the video is an anecdote from a Dallas Cisco users group hosted at Cisco, where a recruiter from TEKsystems — which he describes as a large IT staffing/recruiting firm with a view of the job market — reportedly said network engineering roles were hot and hard to fill, and that engineers who also know some programming are rare ‘unicorns’ employers are specifically looking for. His own response, he says, was to keep pursuing Cisco certification (he lists his CCNA and CCNA Voice and studying for CCNP) while also starting to learn Python through a Udemy course. His advice is to invest a small, regular amount of time in programming — even an hour a week — including Python courses aimed at network engineers that automate routing and switching tasks, rather than trying to become a full developer. The video also covers Cisco Live news of the time, including Cisco DNA, encrypted traffic analytics using machine learning, and the Catalyst 9000 switches’ programmability, APIs and container support, and closes with a tip to get hands-on lab experience with real hardware where possible alongside Packet Tracer/GNS3.

Key takeaways

• Do not choose one or the other: keep the CCNA as the valuable networking foundation and add programming on top of it
• The prized profile, per the TEKsystems recruiter he quotes, is the ‘unicorn’ — a network engineer who also knows some programming — because they are rare and hard to hire
• He expects per-device CLI configuration to give way to controllers, scripting and automation, so programming will become part of every networking, voice and security career
• Start small and regular — for example an hour a week learning Python, ideally via courses that apply Python to network automation tasks
• Hands-on labbing, including physical hardware where possible, builds the confidence that simulators like Packet Tracer and GNS3 alone may not

Episode details: published June 29, 2017 · 15:44 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: Am I Smart Enough to Be a Network Engineer? - CCNA | CCNP Study · Next: 3 Ways to Get Out of a Study Slump - CCNA | CCNP Study →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube