Introduction
There has been a lot of talking about the future of the network engineer for the last couple of years. Many articles have declared that we MUST learn to program or we will be banished from the world by the programming overlords! I definitely do not agree with this bold statement but lately I have started to learn Python. Why?
Why Learn Programming?
As a network architect I probably won’t ever write a line of code or at least very rarely so. So why bother learning?
I didn’t learn a lot of programming back in my days of school. I fiddled around a bit with Basic, some Pascal and then at the university I tried some C# and C++. I never felt connected with programming. I never felt that I was good at it. This surprised me a bit because I’ve always been good at learning things. I’m good at analyzing things, troubleshooting things and I have a strong background in maths and science in general. I had all the skills that good programmers normally have so why couldn’t I learn programming? Because I struggled I didn’t enjoy doing it so I never pushed through until it “clicked”.
Later Continue reading
Other thoughts in advance of Cisco Live.
Edsall discusses what 'application-centric' really means and how webscale players change the industry.
Edsall discusses what 'application-centric' really means and how webscale players change the industry.
Open-O elects Chris Donley as technical steering committee chair.
Todays Weekly Show is a free-wheeling discussion on a variety of topics, including network disaggregation, whether open networking actually means freedom from vendor lock-in (probably not), the rise of 25Gig switching, the end of outsourcing, and more. The post Show 296: Never Free From Vendor Lock-In appeared first on Packet Pushers.
The post Worth Reading: The lizard brain of lizardstresser appeared first on 'net work.