Your First 90 Days as a Technical Manager: What Actually Matters (And What Doesn't)
The first 90 days as a technical manager are nothing like what you expect. The technical fires are manageable - it's the people dynamics, the organizational politics, and the invisible responsibilities that blindside you. Here's what actually matters in your first three months, what can wait, and what nobody tells you until you're already struggling.
The AI Cost Reckoning: When "Replacing People" Costs More Than the People
Companies eliminated positions and implemented AI to save money. The spreadsheets looked great. The ROI was clear. Eighteen months later, they're discovering AI costs more than the people it replaced - but nobody wants to admit it publicly. Here's the math that's not adding up and what's actually happening behind closed doors.
When Your "Quick Win" Becomes a Disaster: Recovering From Failed Initiatives Without Destroying Your Credibility
You pitched it as a quick win. Fast implementation, immediate value, low risk. Three months later it's a mess - over budget, behind schedule, creating more problems than it solved. Your team is frustrated, leadership is questioning your judgment, and you're wondering how to recover. Here's how to handle failed initiatives without destroying your credibility or your team's trust.
Your Engineer Made a Mistake That Cost Money: Now What?
A configuration error takes down the network for 3 hours. Lost revenue: $200K. The engineer who made the mistake is sitting in your office. What you do in the next 30 minutes will define your team's culture, that engineer's future, and your credibility as a leader. Here's how to handle it without destroying trust or enabling repeated mistakes.
The Talent Pipeline AI Is Destroying: Where Do Senior Network Engineers Come From in 10 Years?
Organizations are using AI to eliminate NOC and helpdesk positions to cut costs. In 5-10 years, they'll wonder where their senior network engineers went. If you automate away the bottom of the talent pipeline, you don't have a future - you have a crisis nobody saw coming. Here's the talent time bomb nobody's talking about.
The Politics of Multi-Team Projects: When You Need Other Teams to Deliver (And They Don't Report to You)
Your project success depends on another team delivering their part. They don't report to you. They have their own priorities. Their delays are blocking your progress. And your boss is asking why your project is behind. Welcome to the hardest part of technical management - getting work done across organizational boundaries when you have no formal authority.
Making the Call: When to Build In-House vs. Buy vs. Outsource
Your team wants to build a custom solution. Vendors are pitching commercial platforms. Leadership is asking about outsourcing. The decision seems impossible - each option has compelling arguments and hidden costs. Here's how to actually make this call when you're responsible for the outcome.
Automation Debt: The Graveyard of Good Intentions (And Why Your Automation Keeps Failing)
Every network engineering organization has a graveyard of failed automation attempts - the GitHub repos with one person's commits from 18 months ago, the Ansible Tower license nobody uses, the Python scripts only one person understood who left last year. This is automation debt, and it's costing you more than you think.
The First Time You Realize You Can't Do It All: Delegation for Control Freaks
You became a manager because you were great at the work. Now you're drowning because you're still trying to do all the work yourself. Here's what happens when control-freak engineers try to delegate - the uncomfortable reality of letting go, the mistakes that make it worse, and what actually helps you stop being the bottleneck.
When Good Engineers Become Managers: What Nobody Tells Them (And How to Help Them Succeed)
Promoting your best engineer to manager feels like the obvious move. But technical excellence doesn't automatically translate to leadership effectiveness. Here's what actually happens when engineers become managers, the mistakes they almost always make, and how to help them succeed without losing what made them great engineers.
Explaining Network Engineering to Non-Technical People: How to Make Them Actually Understand (Without Their Eyes Glazing Over)
Your executive asks "why do we need this network upgrade?" You start explaining routing protocols and they've already stopped listening. Here's how to translate network engineering into language non-technical people actually understand - and why this skill matters more than your technical expertise for your career.
When You and Your Senior Engineer Disagree: How to Lead Without Pretending You're Always Right
Your senior engineer says your approach won't work. You think it will. Who's right? How do you lead when the person with deeper expertise disagrees with your technical decision? Here's how to navigate disagreements without damaging relationships, pretending to know more than you do, or undermining your authority.
When Your Team Is Right, and Leadership Is Wrong (And You're Stuck in the Middle)
Your team says the timeline is impossible. They're right. Leadership says it has to be done anyway. Your engineers want to fix technical debt. Leadership wants features. You need tools and training. Leadership says no budget. Welcome to middle management - where you're stuck between technical reality and business demands, and nobody's happy with you.
Inheriting Someone Else's Network: What to Fix, What to Leave Alone, and How Not to Destroy Your Credibility
You just got promoted or changed jobs. Now you're managing a network you didn't design, with decisions you don't agree with, and configurations that make you cringe. Do you change everything? Leave it alone? How do you prove yourself without breaking things or alienating the people who built it? Here's what actually works when inheriting someone else's infrastructure.
Changing Culture as a New Manager: When "We've Always Done It This Way" Is the Enemy
Six months into management, I'm learning that changing culture is way harder than changing technology. You have a title but no political capital. Your team might embrace change, but other departments resist. Here's what's actually working (and what's spectacularly failing) when trying to shift "we've always done it this way" culture.
Managing Your Team Through a Major Outage: The Leadership Test Nobody Prepares You For
Major outages aren't a matter of if, but when. And when they happen, your job as a manager isn't just technical - it's keeping your team functioning under pressure, communicating to leadership, and ensuring you learn without creating a blame culture. Here's what actually matters when everything is on fire.
2025: A Year in Review - From Engineer to Manager to Blogger to... Whatever This Is
A year-end reflection on an unexpectedly transformative 2025 - transitioning into management, growing Layer8Packet, launching a newsletter, and learning that sharing the messy middle of a career journey resonates more than having all the answers.
Your First IT Budget: A Survival Guide for New Managers
So you're a first-time manager and someone just asked you to "create a budget for next year." Welcome to one of the most stressful parts of management nobody prepared you for. Here's what you actually need to know about IT budgeting - the categories everyone forgets, the political landmines, and how to not screw this up.
Job Hopping Every 2-3 Years: Career Strategy or Red Flag?
Should network engineers change jobs every 2-3 years for salary growth, or does loyalty to one company build deeper expertise? From both the engineer's and manager's perspective - the real data on compensation, the trade-offs nobody talks about, and how to think strategically about your career trajectory.
Both Sides of the Desk: Asking for a Raise (The Engineer’s Perspective)
Part 3 of the "Both Sides of the Desk" series tackles one of the most uncomfortable conversations in your career: asking for a raise. From the engineer's perspective, how to know if you deserve one, when to ask, how to build your case, and what to do when the answer is no.