Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up and I will send yoy a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.
What happens when there are no more fires to fight?
The Tree Chopping TrapI’ve been thinking a lot about how network engineers spend their time, and I keep coming back to this metaphor that perfectly captures what I see happening across the industry. Most of us are stuck chopping down trees. Let me explain what I mean. Your day looks something like this: alerts flooding your monitoring system. A switch that’s reached end-of-life but still works fine. Other teams ask why their application is slow. Your inbox has 247 unread messages. Your Slack is a constant stream of red dots. So you do what any good engineer does. You chop down trees. You clear tickets. You configure devices. You update the configurations. You troubleshoot connectivity issues. You attend meetings about meetings. And this work truly matters. It keeps the network running. It keeps users connected. It keeps the business moving. But if this is ALL you do, you’re in serious trouble. The Forest Will Run OutThis is the harsh reality that most network engineers don’t see until it’s too late: If all you ever do is chop down trees, eventually you’ll run out of forest. While you’re deep in configuration and troubleshooting, the industry is moving to software-defined & AI networking. While you’re manually updating firewall rules, Infrastructure-as-Code has become the standard. While you’re troubleshooting that MPLS circuit, companies are migrating to cloud-native architectures. You’re solving today’s problems brilliantly. But you’re not planting any seeds for tomorrow’s opportunities. And when the forest is gone i.e when your skills become commoditized, when your manual processes get automated, when your traditional network architecture gets replaced by something you don’t understand, you’ll be stuck with no way forward. The uncomfortable question: How much of your time is spent chopping down trees, and how much is spent looking for fertile ground? Are you learning Infrastructure as code? Exploring network automation? Understanding how container networking actually works? Testing zero-trust architectures in a home lab? Every time I talk to network engineers about this, I get the same response: “Kayodel, I get it. But I don’t have time. You don’t understand how busy I am.” The operational demands of network engineering are relentless. There’s always another ticket, another outage, another urgent request from leadership. But here’s what I tell them, and what I’m telling you now: If you don’t make time to plant seeds now, you’ll be forced to make time later when you’ve run out of trees and by then, it might be too late. That’s the confronting reality of being a network engineer in 2025. The challenge isn’t choosing between operational excellence and future readiness. It’s finding the balance. It’s carving out 30 minutes three times a week to learn something new. It’s saying no to that fifth meeting so you can experiment with AI Networking. It’s blocking off Friday afternoons for deliberate learning. Because the cost of not doing this is your career. Your Action Items (The Part Where You Stop Reading and Start Doing)So here’s what I want you to do this week:
The network engineering landscape is changing faster than ever. The skills that made you valuable five years ago won’t be enough five years from now. You can either spend your career chopping down trees until the forest runs out or you can start planting seeds for tomorrow’s growth. The choice is yours. But make it quickly because the forest is smaller than you think. Until next time, Stay curious. P.S. — What’s one seed you’re going to plant this week? Hit reply and let me know. I read every response. P.P.S. — If this resonated with you, forward it to that network engineer friend who’s very good at putting out fires. They’ll thank you later. |
The Modern Engineer
Join 1k+ other forward-thinking professionals who receive the weekly newsletter, where I provide actionable strategies, insights and tools to escape the grind and build influential, future-proof careers. Sign up and I will send yoy a FREE copy of my 5-Stage playbook to multiply your impact and build a career that AI can't replace.
Hello Reader, I spoke with an old friend last week. He told me he spent 4 years as a senior engineer watching less experienced engineers get to the next level ahead of him. His designs were cleaner. His solutions were faster. His technical reviews were thorough. But he kept getting the same feedback: "You need to be more visible and strategic" He thought that meant talking more in meetings. He was wrong. What he lacked was influence at work The Real Problem Here’s what actually happens when...
Hello Reader, Understanding this distinction would have saved me years of frustration in my engineering career. Every organization has two kinds of engineers. There are functional engineers and there are vital engineers. Most people never realize this, and it keeps them stuck far longer than necessary. I learned this the hard way, after confusing output with outcome for a long time. At first glance, functional engineers look impressive. They deliver tickets, close incidents, follow processes...
I’ve spent the last few years studying how influence actually works inside organizations, especially among engineers, ICs, and systems thinkers. Not the loud kind. Not the political kind. Not the manipulative kind. The kind that compounds quietly. Below are 26 influence rules I’m following going into 2026 and beyond. Principles for building credibility, trust, and authority without losing yourself in the process. Avoid unforced credibility errors. Most influence is lost through small,...