The Art of Network Engineering

Great blog post from John Capobianco about our Hello World for AI episode. Check it out!

For years, network engineers were told: “Learn Python or fall behind.” That advice just expired. Andy Lapteff 🛠️💬 just walked through a real AI “Hello World” with John Capobianco where they: - Connected Copilot and Claude to NetBox with the Netbox MCP Server - Queried network data in natural language - Generated real outputs - Fixed errors using AI - No Python required This isn’t hype. It’s a shift in how work gets done. The barrier to entry just dropped. The expectations just went up. If you haven’t started with AI yet, this is your moment.

One of us! Congrats Wilmir :)

A seemingly impossible challenge from a manager on a Friday afternoon: create a zero-configuration, topology-independent distributed algorithm that scales with constant memory, even for "drunken monkeys" plugging things together. The constraint was no changes to the deployed system, and the ideal scale was constant memory usage regardless of network size. The manager's departure the following week left little room for clarification. Remarkably, by Tuesday night, the trivial nature of the solution became clear, resulting in a 25-page specification. The implementers later brought it to life in under two months, without a single question. #DistributedSystems #ComputerScience #Innovation #ProblemSolving #AlgorithmDesign

Inventing Spanning Tree in a weekend? This highlights a remarkable ability to simplify complex problems. While many grapple with learning and implementing such concepts over extended periods, the ability to conceptualize and spec it out in mere days points to a unique problem-solving approach. It's a reminder that sometimes, stepping back and viewing challenges from different perspectives can reveal solutions that appear obvious in hindsight. What strategies do you employ to approach complex technical challenges? #ProblemSolving #Innovation #Networking #Engineering #TechLeadership

In engineering and design, true innovation stems from understanding and building upon what came before, not from reinventing the wheel in isolation. It's a counterproductive mindset to claim ignorance of existing solutions. Embracing and learning from prior work, even if attributed, accelerates progress. Ignoring established alternatives leads to fragile, inefficient outcomes. Progress is best achieved by thoughtfully considering existing knowledge, rather than striving to invent in a vacuum. #Innovation #Engineering #ProblemSolving #ContinuousImprovement #Technology

Reflecting on network protocol design, CLNP (ISO's IP equivalent) offered a more elegant solution than IP. Unlike IP, where each router hop requires a Layer 3 address change, CLNP utilized a 14-byte prefix for broad network routing. Within this prefix, the remaining 6 bytes enabled routing to specific end nodes. This design simplified routing significantly and eliminated the need for ARP within the network segment. Furthermore, CLNP supported flat address spaces within a cloud, allowing devices to move freely while retaining their Layer 3 address. It also boasted zero-configuration capabilities, contrasting sharply with IP's manual address configuration. This architectural superiority in simplicity and flexibility warrants a closer look, even decades later. #Networking #Protocols #CLNP #IP #NetworkDesign #TechHistory

Our upgraded mobile podcast studio made it home safely from Tech Field Day #NFD40. We recorded 4 in-person episodes with industry titans, and we can’t wait to share them with you. Stay tuned, and thanks for listening 🎤❤️

Tech careers don’t just happen. They’re engineered, just like networks. If you’re a network engineer feeling stuck or wondering why your technical skills aren’t translating into promotions, this is for you. It covers the "invisible" side of the job: visibility, networking, and why your resume matters less than you think. #NetworkEngineer #CareerDevelopment #TechCommunity

On the road again 🎤