Leading When You Still Feel Like You're Learning

I’ve been a software engineer for years, long enough to know the weight of a production issue, the reality of tight deadlines, and how “just one more change” can wreck an entire week. Most of my career has been deep in a very specific corner of tech: enterprise mortgage systems, specifically Encompass development.

Learning development here was crazy. It’s a world with its own rules and limitations. It’s C# development, but with custom SDK’s that don’t seem to follow standard conventions. Most of the tricks I’ve learned were from other far more experienced and talented devs teaching me “hacks” and tricks. It doesn’t map neatly to the stacks you see in blog tutorials, conference talks, or coding interview prep sites.

Now I’m transitioning to a leadership role, running a team, making calls, setting direction. This all feels scary, even if I’ve been unofficially doing it for a long time. I’ve been extremely fortunate to be surrounded by some exceptionally talented individuals, and I’ve always been quick to take their lessons to heart. I’m still teaching most of their lessons to others to this day.

The Fear of Exposure

In the back of my mind, there’s always this nagging thought: If I start writing about programming, will it be obvious I’ve spent most of my career in this niche? Will other developers read my stuff and think, “That’s junior-level”? Will it make it obvious that I landed this position without having the breadth of experience they’d expect from a senior lead? I know, very typical Imposter Syndrome. It’s real, the anxiety is crippling at times.

It’s not that I can’t build things. I get pigeon-holed in some of the antiquated tech that’s required for some of this very specific software to run. Outside my domain, the ground feels less familiar. Interviews outside this industry have shown me gaps. Architecture theory, systems design, certain language patterns—they’ve all been weak spots at times.

The Truth About Leadership

Here’s what I’ve figured out so far. Leadership isn’t about knowing every single thing. There are phenomenal leaders I work with to this day that probably say, “I’m not sure, I’ll have to find out,” on probably a daily basis. Great leaders make good technical decisions when it counts. They clear the path for the team. They help deliver something they can be proud of. It’s about balancing speed and quality.

Specialization doesn’t make you less capable. It means you have depth in an area where other developers would sink in a week. Pair that with the willingness to learn outside your comfort zone and you can be more effective than someone who knows a little bit of everything but can’t deliver when it matters.

Why Life After AI Exists

We’re all working in a new reality now. AI can write boilerplate in seconds, refactor files, even suggest architecture diagrams. That’s exciting because of the speed, but it’s also unsettling because it raises the question: what happens to us?

Life After AI is about the answer to that. It’s about building a career and a life that still matter when AI is everywhere. It’s about learning to work with the tools instead of being replaced by them. And it’s about accepting that you’ll never know everything, but you can keep learning anyway.

To be clear, I use AI extensively. It’s literally my coding buddy. I have it check over my work, look for redundancies, recommend better ways of writing code. I’ll try to teach some of the techniques I use. I don’t agonize over prompts - I’ve never seen that much value in them. That said, I know of a few tricks that seem to get me the best results.

If you’ve ever felt like you’re behind, stuck in your niche, or unsure if you belong in the room where the decisions are made, you’ll likely feel right at home here. We’re not here to fake it, we’re here to grow.

Welcome to Life After AI.

Subscribe now