The Coding Networker Blog is about programming from the perspective of a Network Engineer. It’s primary my personal documentation of some of my projects and use-cases that apply mostly to some common tasks within the world of a Network Engineer. Furthermore, I like to give you the confidence that you don’t need to be a full time developer to be effective. I encourage everybody to have at least some basic knowledge in this area, because it will save you a lot of time in the long run.
The heavy interest in SDN technologies back in 2015/2016 showed me quite early that automation and programming/scripting is a valuable skill. To learn python and some other topics within the “software world” was one reason, why I started the blog.
I hope that the content on this blog is helpful for you and if you have any feedback or find typos, please drop me an email at firstname.lastname@example.org.
About the author
I’m Henry and I’m a Network Engineer and hobby programmer. Since 2007 I have worked for a large service provider in Germany. During my career I walked through many roles within the network industry: from network implementation to design, from pre-sales to operations. I also hold some certifications, including the Cisco CCNP Routing & Switching, CCDP and some Specialist Certifications. Besides my daily job, I’m a hobby programmer. I learned some programming languages in the past, starting with C/C++ when I was 13 years old. That was one reason, why I decided to start a career within the IT industry.
In 2015 I decided to start this blog to document my learning progress in the area network automation with python and to share some of my personal side project’s. Today, it’s a journal for me to document how I solved certain use-cases using python and other software tools.
The contents of this blog represents my personal opinions and experiences. They are not related to my employer. All scripts can be used without any warranty at your own risk. Larger projects are usually licensed under MIT (please see the license note included in the project repositories).
The legal disclosure is available here