Insight: Fifteen Years in IT
Over fifteen years, I’ve learned that technical skill may open doors, but judgment is what determines which ones are worth walking through.
Fifteen years. That’s enough time to watch technology stacks rise and fall, to see a help desk tech grow into an architect, and to realize that many of the things you once thought mattered… didn’t. At least not in the way you expected.
This isn’t a victory lap. It’s a reflection — honest, imperfect, and hopefully useful for anyone early in their career or somewhere in the middle, wondering what it all adds up to.
What I Got Right
1. I Let Curiosity Be My Compass
I didn’t build my career by chasing titles. I chased the work that made me lean in — the messy systems no one understood, the recurring problems everyone tolerated, the gray space between teams where communication broke down.
I wasn’t driven by org charts. I was driven by the question: Why does this keep happening, and how do we fix it?
That instinct led me into difficult corners of the business — but also into the most meaningful work I’ve done. I didn’t always end up in the spotlight, but I ended up where the real problems lived. Over time, that built something more durable than a title: trust.
2. I Learned to Speak Two Languages
Being technical is one skill. Making complexity understandable is another.
Early in my career, presenting to executives made my heart race. I preferred terminals to conference rooms. But over time I realized something important: most people aren’t looking for technical mastery in those moments. They’re looking for clarity, reassurance, and a path forward.
Once I stopped trying to sound smart and focused instead on helping people understand, everything changed.
That shift — from proving expertise to creating clarity — built more influence than any certification or platform ever could. Communication with empathy and precision has outlasted every tool I’ve worked with.
3. I Said Yes — and Then Figured It Out
Impostor syndrome followed me for years. Every promotion felt slightly premature. Every new system felt one step beyond my depth.
But some of the best growth in my career came from saying yes before I felt ready.
New platforms. Large migrations. Leadership responsibilities I didn’t feel qualified for. I said yes — and then I learned fast.
What surprised me wasn’t how much I didn’t know. It was how much I could figure out under pressure.
Over time, discomfort stopped feeling like danger and started feeling like expansion. Experience doesn’t eliminate uncertainty. It builds resilience. Eventually, the voice that whispers “You don’t belong here” gets quieter — replaced by one that says, “You’ve handled harder things before.”
What I Got Wrong
1. I Thought Hard Work Spoke for Itself
It doesn’t. At least not always.
Early on, I assumed effort and outcomes were obvious. That someone would notice the late nights, the production saves, the clean implementations.
What I learned is that organizations value contribution differently. In some places, deep technical work is celebrated. In others, it’s expected quietly while visibility and cross-team influence drive recognition.
Recognition often flows where visibility lives.
That’s not a flaw — it’s a system. Once I understood that, I stopped assuming the work would speak for itself. I learned to document impact, communicate outcomes, and translate technical value into language the organization understands.
Not for credit — but for clarity.
2. I Ignored My Limits (Until They Broke Me)
There was a version of me that wore burnout like a badge of honor.
I skipped vacations. Answered 3 a.m. alerts out of guilt. Stayed reachable long after the day was done. I believed being indispensable meant being always available.
It wasn’t dedication. It was over-identification.
Over time, the cost showed up — mentally, physically, relationally. IT never truly slows down. There is always another migration, another incident, another deadline. If you don’t build boundaries, the work will consume the space you leave open.
Now, boundaries aren’t optional. They’re strategic.
I take time off without guilt. I disconnect when the day ends. I protect margin not because I care less — but because I want longevity in this field.
The real flex? Learning how to walk away from a fire that isn’t yours to put out.
Looking Back — and Ahead
Fifteen years in, growth feels less linear and more layered.
Every organization operates differently. Culture matters. Leadership matters. Some environments reward deep technical mastery. Others reward influence and visibility. Neither is right or wrong — they’re simply different.
What matters is alignment.
Between your values and the organization’s priorities.
Between your working style and the systems around you.
Between your ambition and your sustainability.
The most valuable thing I’ve built over the past fifteen years isn’t a platform, a migration plan, or a governance framework.
It’s judgment.
Judgment about where to invest energy.
Judgment about when to push and when to pause.
Judgment about which problems are worth solving — and which ones aren’t.
If there’s anything I’d offer someone earlier in their path, it’s this:
Chase understanding over titles.
Build clarity, not just systems.
Protect your sustainability.
And don’t be afraid of discomfort — it’s often where your next level lives.
Fifteen years in, I’m still learning.
But I’m learning with intention now.