A Journey, Not a Manual
I started writing this book thinking it would be a methodology guide. It became a memoir.
The Architect and The Navigator: Building with AI is a record of one year of building real client projects with AI as a collaborative partner — and what I discovered about experience, craft, and what comes next.
The Architect and The Navigator
Closer to a memoir than a manual.
What This Book Is
Most professionals use AI for snippets — a function here, a rewritten paragraph there. They're leaving most of the value on the table.
This book is what happened when I stopped using AI that way.
Over the course of a year, I worked with AI on five real client projects. A SaaS platform built from a brain dump. A 150-endpoint enterprise migration completed in three weeks. A complete government proposal produced in five days. Two simultaneous planning engagements where the deliverable was a blueprint someone else would execute. A federal interpreter services platform built from a functional requirements document to a live government demonstration in five days.
The methodology that emerged is real. Six core practices across two layers. Two roles you play simultaneously: The Architect, who sets direction, and The Navigator, who steers through AI's output. A four-phase process — Define, Plan, Execute, Deliver — that ties them together.
But the methodology turned out to be the easy part. The harder part, the part I kept coming back to, was what the work was doing to me. The questions I started asking about where this all leads. The honest uncertainty about what AI actually means for experienced people who have been doing this for decades.
This book is the record of that year. Real projects. Real exchanges with AI. Real mistakes. Real bugs caught by experience that AI couldn't catch on its own. Real questions I'm still wrestling with.
The Architect and The Navigator
Through a year of real production work, two roles emerged that determine whether AI collaboration produces results worth shipping.
Most people only play one. The professionals who get real results from AI collaboration learn to play both.
The Architect
Sets direction. Communicates constraints, context, and strategic decisions. Writes the blueprint in words before AI touches the code. The experienced judgment that determines what gets built and why.
The Navigator
Steers through AI's output. Catches assumptions that don't hold. Pushes back when something feels off. Validates against real behavior, not polished-sounding claims. The practitioner's instinct that determines whether the result actually works.
The Complete Book
A prelude, eight chapters, and three parts. Built from real projects. Honest about what actually works — and what I'm still figuring out.
Why this book became a memoir, what the reader is actually about to read, and who it was written for.
Chapter 1: The Architect and The Navigator
The two roles you play simultaneously when collaborating with AI on real projects. Why experienced professionals are best positioned to leverage AI. The Craft Paradox — why the people most qualified to use AI are the ones most resistant to it.
Chapter 2: The Playbook
Six core practices across two layers, plus the four-phase Define, Plan, Execute, Deliver process that ties them together across real project lifecycles.
Chapter 3: FileCourier
Building a B2B SaaS platform from a brain dump. The methodology emerging through instinct before I had names for any of it.
Chapter 4: The POD Migration
Migrating 150 endpoints from a legacy enterprise stack to Go in three weeks. The methodology becoming deliberate and repeatable.
Chapter 5: The Government Proposal
Producing a complete government RFP response in five days. The methodology working beyond code, forcing me to articulate the "what" and "how" I'd never documented before.
Chapter 6: The Integration Blueprint and The Legacy Roadmap
Two simultaneous projects where the deliverable wasn't code but the plan a development team would execute. The methodology becoming transferable.
Chapter 7: CourtLingo
A federal interpreter services platform built from a functional requirements document to a live government demonstration in five days. The methodology proven universal — working on a domain I'd never touched before.
Five case studies. Five domains. Each one built the methodology further — from instinct, to deliberate practice, to transferable system.
Chapter 8: The World You're Building Into
The economic, infrastructure, and societal realities shaping where AI-accelerated development is headed. What I hope. What I'm uncertain about. What I think experienced practitioners should do right now.
Who This Book Is For
This book is for the practitioner wondering if their experience is becoming obsolete or becoming more valuable than ever.
For the senior developer tired of being told their craft is being automated away.
For the architect, the CTO, the consultant, the team lead — anyone who has been doing this long enough to know better than to believe the loudest voices in the AI conversation. And for anyone who has ever enjoyed watching something take shape under their hands, and wants to know if AI makes that feeling bigger or smaller.
"The methodology was always going to be useful to someone. The journey turned out to matter more."
Jae S. Jung
Jae S. Jung has been building since 1997 — infrastructure, SaaS platforms, legacy migrations, distributed teams across four continents. Not drawing diagrams and handing them off. Actually building.
When someone says "this is broken, let's fix it," his first instinct isn't to patch. It's to step back and ask: what's actually wrong here? Quick fixes feel productive. But they often cost more in the long run — more rework, more surprises, more frustration. The better path is a reasonable pause to find the real problem, then solve it once.
That's the same philosophy and culture he brings to WAM DevTech — the core principle it was founded on. AI doesn't replace any of that. It amplifies it.
This book is the record of what amplification actually looks like over a year of real work.
Stay in Touch
The book is complete. The conversation is just starting. If you want updates on what comes next — new case studies, thoughts on AI collaboration, and occasional insights I only share with readers — sign up below.