I forgot what it felt like to just build. Then I remembered.

I started building things with x-y pixel coordinates on a screen that glowed green. Then FORTRAN at Virginia Tech. Assembly language. 4GL. My first HTML page for a global markets class in 1995. Then more programming languages: Perl, PHP, ColdFusion, JavaScript, .NET. Then systems: DOS, UNIX, Windows NT, Linux, Ubuntu. Then infrastructure: cloud, AWS, and more. You get the point. First I was just building code. Then I was building and architecting and managing teams to build enterprise-level applications supported on complex architecture.

Each one felt like Lego pieces snapping together. That pure, simple joy of making something that didn't exist before. You write a line of code, something happens on the screen, and for a moment the whole world makes sense. Every developer who's been in this long enough knows that feeling. It's why we got into this in the first place.

But somewhere along that progression from code to systems to infrastructure to teams, the feeling changed. The work became less about building and more about managing. Deliverables. Schedules. Scope. I was still in technology. I was still making things happen. But I wasn't the one snapping the pieces together anymore.

Somewhere along the way, I stopped feeling it.

The Slow Disappearance

It didn't happen all at once. There was no moment where I decided to stop building. It happened the way most things disappear — gradually, one responsibility at a time.

I moved into lead roles. Architecture reviews instead of writing code. Then management. Then executive leadership. Suddenly I was overseeing multiple projects, sitting in constant meetings with Product Managers and Product Owners. I wasn't talking to Tech Leads about implementation details anymore. I was too busy managing the daily operations of a business: budgets, hiring, client relationships, strategic planning.

The work was important. I was good at it. Scaling a team from 2 to 20, supporting a platform that processed over $100 million in revenue — that matters. But the Lego feeling was gone.

I think a lot of senior people in this industry know exactly what I'm describing. You got into technology because building things gave you energy. Then you got promoted away from the thing that gave you energy. And nobody tells you that's what's happening while it's happening. You just wake up one day and realize you can't remember the last time you made something from nothing with your own hands.

What AI Changed

When AI started becoming capable enough for real work, I didn't see it as a threat. I saw it as something I wanted to try. Not because of the hype. Because I'm a builder. I've always been drawn to new tools.

But I didn't expect what happened next.

The first time I used AI as a full collaborator — not for snippets, not for quick answers, but for an actual production project — something shifted. I was back in the role of the person with the idea. Snapping pieces together. Seeing something take shape in real time that didn't exist an hour ago.

The Lego feeling came back.

Not because AI does the building for me. That's the part people get wrong. AI didn't replace the joy. It removed the barriers that had been blocking it. The tedious parts that used to drain hours — boilerplate, scaffolding, researching syntax in an unfamiliar language — AI handles those. What's left is the part I actually love. The architecture. The decisions. The creative act of figuring out how pieces fit together.

For the first time in years, I was building again. Real things. A SaaS platform in languages I'd never used in production. A 150-endpoint API converted to a modern stack. A government proposal that would have required a team of three. Not managing someone else's build. Building it myself, with AI as my collaborator.

The Part Nobody's Talking About

The New York Times recently ran a piece on what happens to programmers when AI writes the code. The anxiety is real. I feel it too, for the developers navigating this shift.

But reading it, I found myself thinking about something the article missed entirely.

There's a generation of senior technologists — architects, CTOs, VPs of engineering, technical directors — who haven't written production code in years. They moved up. They manage. They strategize. They review. But they don't build anymore.

AI gives that back.

Not by replacing their teams. By giving them a way to be hands-on again. To prototype an idea in an afternoon instead of scheduling it into next quarter's roadmap. To test an architectural approach by actually building it instead of drawing it on a whiteboard. To feel the Lego pieces snapping together again.

That's not a story about loss. That's a story about rediscovery.

The Joy and the Weight

I want to be honest about something. The Lego feeling came back. So did the exhaustion.

When you build at the speed AI enables, there's no natural friction. No waiting for a build to compile. No pausing to look up documentation. No break between deciding what to do and doing it. The output comes immediately. And every few minutes, there's another decision that needs your full attention.

Here's what a session actually looks like: I'll start with an architectural idea at 9am. By 10:30, there's a working prototype. By noon, I've iterated through three major design decisions, refactored the data model twice, and built out an entire feature set. The code exists. It works. And my brain is completely empty. Not tired — empty. Like I've been sprinting for three hours straight, except the sprint was entirely mental.

The joy is real. The cognitive load is also real. I've had sessions where I produced more in three hours than I would have in a week — and then hit a wall so hard I couldn't think for the rest of the day.

That's the tradeoff nobody warns you about. AI gives you back the thing you love. It also removes the friction that was secretly giving your brain recovery time between bursts of creative work. Managing that is something I'm still figuring out.

Why This Matters More Than Productivity

Every article about AI and development focuses on productivity. How much faster. How many more endpoints. How much code. The numbers are real and they're impressive.

But for me, the most important thing AI did wasn't making me faster. It was making me a builder again.

After years of managing, reviewing, and strategizing — important work, necessary work — I'm back to making things. That's not a productivity story. That's a purpose story. And I think there are a lot of people in senior technical roles who are one real AI collaboration session away from feeling it too.

The Lego pieces are still there. The joy of snapping them together never left. It just got buried under years of career progression.

AI is the shovel.

I'm writing a book about the methodology behind all of this — how experienced professionals can collaborate with AI to build at a level they haven't operated at in years. The joy of building is where the journey starts.

The Architect and The Navigator: Building with AI is available now on Leanpub.