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 Influential 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, There is a point most engineers hit where progress quietly stalls. You are doing solid work, you are reliable, easy to collaborate with and technically competent. From the outside, nothing looks wrong. But the interesting projects start going to the same few people, promotions feel harder to reach, and your ideas land in the room but do not travel beyond it. What is uncomfortable is that you are not failing. You are just indistinguishable. Most engineers respond to this by...
Hello Reader, Have you ever watched someone else get picked for an opportunity you knew you deserved? You work hard, deliver consistently, and show up every day. And then you watch someone else get picked for the opportunity you wanted: a promotion, a project, or a seat in a room you know you belong in. It hurts in a quiet way. You don't complain or make a scene. You nod, tell yourself to keep your head down and do the work, because that's what responsible people do. That's what you were...
Hello Reader, There is a quiet instinct many people develop as they get more competent. Once you know your work is solid, you try to remove anything that might undermine it. You ensure that small slips that might make you look less capable are gone. The goal becomes clear. Do not give anyone a reason to doubt you. What is interesting is that this instinct often backfires. You have probably seen it happen. Two people demonstrate roughly the same level of skill. One is flawless. The other makes...