Last quarter I wrote that runways aren't built for their own sake — they're built so other things can take off.
This is the takeoff.
I've written up the full account of building the AWS landing zone solo. It's on Medium, and the title says most of what I want to say about it:
I Built an AWS Landing Zone Alone — The Architecture Wasn't What Cost Me
The architecture was the part I knew how to do. Account structure, guardrails, identity model, centralised egress — those are solved problems if you've done the reading and you're willing to be careful. That work is demanding, but it's demanding in a way you can plan for.
What actually cost me was everything around it. I've put that in the article rather than here, because it deserved the space.
Something I've come to realise about the role.
Solution architect. Enterprise architect. Those are the titles, and they're accurate as far as they go. But they describe the diagrams, and the diagrams are maybe half of it.
The other half is what I've spent this year quietly building alongside the platform: knowledge bases, delivery platforms, working processes, AI harnesses for cloud deployments and application architecture. Scaffolding, essentially. The things that let a team move without an architect standing next to them.
I said last quarter that architecture living in one person's head is a dependency, not architecture. Building the landing zone alone made that concrete in a way I couldn't have argued myself into. A system only one person understands is a system with an expiry date attached to that person.
So the work now is transfer. Getting what I know out of my head and into a form the team can pick up, use, and eventually improve without me.
And the skills gap is real. AI has moved the floor and the ceiling at the same time. Engineers who lean into it are compounding fast; engineers who don't are drifting further behind every quarter — through no fault of their own, usually just a lack of a clear on-ramp.
Building that on-ramp is, I think, the most valuable thing I can do right now. More valuable than any single architecture I could draw. Lifting the people around me isn't adjacent to the architecture work — increasingly it is the architecture work.
The platform is up. The applications are running. The edge is wired.
Now comes the part I'm actually more interested in: watching other people fly it.