HN807: A ‘CLI Lifer’ No More
Andy Lapteff once considered himself a ‘CLI lifer.’ As a network engineer he wasn’t interested in Python. He didn’t want to learn to code. He had no desire to embrace any of the developer-like processes and tools creeping into the profession, particularly around network automation. That’s changed. On today’s Heavy Networking, Andy shares the professional, ... Read more »

Andy Lapteff, a network engineer who once proudly identified as a "CLI lifer," has undergone a significant transformation in his professional approach. For years, he resisted the trend of network automation and the integration of developer-like processes and tools into his field. However, his perspective has shifted dramatically, and he now embraces the power of coding and automation.
In the early days of his career, Andy was content with the command-line interface (CLI) as his primary tool. He believed that the traditional CLI approach was sufficient for managing networks and solving problems. He had no interest in learning Python or any other programming language, viewing coding as a domain reserved for developers. This mindset allowed him to focus on his core responsibilities as a network engineer, which he felt were best handled through direct interaction with network devices via the CLI.
However, as the networking landscape evolved, so did the demands placed on professionals like Andy. The increasing complexity of networks and the need for faster, more efficient problem-solving methods forced many network engineers to reconsider their approach. Automation became a necessity, and with it, the need for scripting and coding emerged. Andy, initially reluctant, found himself unable to ignore these changes any longer.
The turning point for Andy came when he was tasked with automating a repetitive and time-consuming network configuration process. Instead of manually configuring each device, he decided to write a script in Python to handle the task. To his surprise, the script not only saved him significant time but also reduced the likelihood of human error. This experience marked a pivotal moment in Andy's career, as he realized the potential benefits of embracing coding and automation.
As he delved deeper into network automation, Andy discovered a wealth of resources and communities dedicated to sharing knowledge and best practices. Platforms like Ansible, Puppet, and Chef became essential tools in his toolbox, enabling him to manage complex network infrastructures with ease. He also found that learning Python opened doors to new opportunities, such as working with network monitoring tools and analyzing network data.
Andy's journey from a CLI lifer to an advocate for network automation is a testament to the changing dynamics of the networking profession. The integration of coding and developer-like processes has become an essential part of network engineering, and professionals who resist these changes risk falling behind.
Today, Andy shares his experiences and insights on Heavy Networking, a platform where he educates others about the benefits of adopting automation and coding in network engineering. Through his articles and videos, he encourages his peers to embrace these tools and techniques, helping them stay current and effective in an ever-evolving industry.
Andy's transformation highlights the importance of adaptability and open-mindedness in the face of technological advancements. By shifting his perspective and learning to code, he has not only enhanced his own skills but also improved the efficiency and reliability of his network operations. As the networking world continues to evolve, Andy's story serves as a reminder that even the most stubborn of CLI lifers can embrace change and thrive in a new era of network engineering.










