Stepping Back From Full-Time Coding: What a Year of Building WITH AI Did

A year ago, I was an organic developer. Every line of code came out of my own hands, one keystroke at a time. Today I'm stepping back from full-time coding — and I want to be clear about what that actually means, because it's not the story people expect.

It's not "AI took over and I stopped." It's that a year of building *with* AI turned me from a developer into an architect.

The difference between renting and building

The easy path this past year would have been to rent tools — stitch together whatever was on offer and hope it fit. I went the other way. I built the pieces I kept wishing existed, and I ran them on hardware we own, so the work stays close.

It's worth being honest about what the old days felt like. My day used to run as a single queue: I'd context-switch through projects one at a time, holding each one in my head until I could get back to it, and quality was something I bolted on at the end — a final pass I hoped I had energy left for. Now the shape of the day is different. The work moves in parallel, and the checks live inside the flow instead of at the finish line. It's less a dramatic scene and more a felt shift: the friction I used to absorb by hand is now absorbed by systems I designed on purpose.

Four of those pieces carried the year:

ObraHaus. The studio itself — the umbrella over every app and tool I ship. It's the north star all of this is in service of: one operation where the products, the infrastructure, and the way I work all belong to the same place instead of being rented and stitched together from parts I don't own. Everything I build runs on hardware I own, in a shape I designed, and it all lives under one roof. That's the whole point — not a pile of disconnected subscriptions I'm renting and hoping stay compatible, but a single coherent operation where each piece knows about the others. When I ship a new app, it lands inside something, not next to it. ObraHaus is the thing that makes every other piece on this list add up to more than the sum of its parts.

My own multi-project driver. A fleet of delegated workers that lets me run several projects at once instead of context-switching through them one at a time. In practice, ObraHaus and the other projects move in parallel rather than waiting their turn in a single queue — work advances on several fronts at once instead of stalling behind whatever I happened to be looking at. Some of you might remember my old post about going from VSCode to Coder — the tablet-coding adventure, the Proxmox home lab, the Terraform fails. I stood up a TestCoder setup on my own Proxmox cluster expecting it to be just another GitHub Codespaces, and it turned out to be much more than that: I was running my own environment on my own hardware, being my own driver. Here's the twist. In the age of AI, that exact instinct — owning my own hardware, being my own driver — is what now lets me be my own multi-project driver, running several projects at once. Right now it feels like every developer is running to the Apple Store to buy a MacBook Pro with the most memory they can get, then flexing the chunky laptop at Starbucks. Meanwhile, if you know me in real life, you'd catch me roaming with just a thin little 8GB MacBook Pro — or even just an iPad — and still driving multiple projects at once, same as those devs with the big chunky machines. The leverage is in the systems I built and own, not in the hardware I carry. This is the thing that changed my days the most — work moves forward in parallel instead of in a single queue.

Defender. A PR review layer built on Claude Code that checks structure and security on every single pull request. This one changed a habit I didn't even know was costing me. Review used to be a final gate I had to remember to open — I'd finish the work, then, if I had the discipline that day, go back and actually look at what I'd done for structure and security holes. Half the time the checking was the thing that got skipped when I was tired. Now, because it runs on every PR, the checks are already there by the time I look. I open a pull request and the review has happened — structure and security both. Quality stopped being something I bolted on at the end and became part of how the code arrives. The before was "hope I remember to check"; the after is "it's already checked."

My second brain. An internal ops layer that holds the whole operation so I don't have to keep it all in my head. It remembers, it links what belongs together, and it surfaces what matters when it matters. Before this existed, the context for everything I was running lived scattered across my attention — half in my head, half in notes I'd lose, all of it decaying the moment I switched projects. Now the operation has a place to live that isn't me. The threads connect themselves, the important things rise to the top instead of getting buried, and I can trust that what I need will be waiting when I come back to it. It's the difference between carrying the whole thing in working memory and being able to set it down knowing it's held.

From developer to architect

Here's the real shift. I used to spend my day *inside* the code. Now I spend it deciding what should exist, then letting the systems I built carry the work forward. I still make the calls that matter. I just make far fewer of them by hand.

That's the honest version of "building with AI." It isn't replacement. It's leverage. You stop being the person who types everything and become the person who designs how the work gets done — and then makes sure it got done right.

The honest trade-off

I don't want to make this sound frictionless, because it isn't. Stepping back from the keyboard means trusting systems to do work I used to do by hand, and that trust doesn't come free. There's always a pull to just reach in and type the thing myself. It's faster in the moment, and it *feels* like progress. The hard part is resisting that pull — slowing down to design a system well instead of racing to type fast. A good design pays off later, not right now. Some days I miss the simple satisfaction of a line of code that just works. But the leverage compounds — and only if I do the slower, less flattering work of building the thing right instead of doing the thing myself.

The altitude

Stepping back from full-time coding isn't stepping away from the work. It's climbing to the altitude where I can see all of it. Being an architect means making fewer decisions but higher-leverage ones — deciding what should exist, then verifying it actually got done right, instead of typing everything into being myself.

Here's what that looks like on an actual day now. I open up and review what the fleet and Defender produced overnight — the PRs that moved, the checks that already ran, the work that advanced while my attention was elsewhere. I read it, I catch the calls that matter, and I steer. Then I spend the real thinking on the next question: what's the next thing that should exist? I'm deciding what to build far more than I'm building it by hand. I still get into the weeds when a decision demands it — but it's a decision, not a reflex to type every line.

And I'll be honest about why this works at all: it only works because the systems underneath are ones I built and trust. The driver, Defender, my second brain — they're not rented black boxes I'm hoping behave. They run on hardware I own, in a shape I designed, so when I step back I'm not stepping into the dark. A year of building with AI is what got me here, and the tools I built along the way are the proof.

Let's talk

Here's where I actually need your help. I've climbed to the architect altitude, and now I'm genuinely unsure which way to grow next — so I'm asking you.

Do I keep sharpening the IT and engineering side, going deeper on the technical craft that got me here? Or do I lean into people skills and marketing, the muscles a founder eventually can't avoid? Should I go chase a Solutions Architect cert, or a PMP, or start an MBA? I keep turning these over and I don't have a clean answer.

So tell me honestly — if you were in my seat, which way would you grow? I'd really value your take. Reach out, leave a note, argue with me. I'm figuring out the architect thing in the open, and I could genuinely use the advice.