A Journey, Not a Manual

I started writing this book thinking it would be a methodology guide.

I had spent the better part of a year working with AI on real client projects, and a pattern had emerged. Six practices. Two roles. A four-phase process. Things I was doing instinctively at first, then deliberately, then well enough that I could see other people benefiting if I shared them. The plan was simple. Document the methodology, package it into a book, sell it to professionals who wanted to work with AI more effectively. A practical guide built from real engagements.

That's not the book I ended up writing.

Somewhere around the third chapter, I noticed that the methodology was the easy part. The hard part — the part I kept returning to — was what the work was doing to me. I'd missed building. I'd lost the Legos feeling somewhere along the way. AI brought it back, but it brought it back changed. I was still figuring out what that meant for my career, my business, my profession, and the broader question of what experienced people are actually for in a world where the tools have started to do the typing.

The methodology was supposed to be the destination. It became the connecting thread.

What the Book Actually Is

What you're holding is closer to a memoir than a manual. It's a record of the year I spent rediscovering how to build, told through five real projects, with the framework I developed along the way as the structure that holds it together.

The framework is real. The practices work. I use them every day, I teach them to clients, and I believe they'll help you. But they're not why I kept writing.

I kept writing because I started having conversations with myself about things I hadn't questioned in decades. Why we work the hours we work. Whether the AI hype is real or manufactured. What the multiplier effect actually means at scale. Whether my experience is becoming obsolete or becoming more valuable than it's ever been. Whether the people writing the loudest takes about AI replacing knowledge workers have ever actually used it on a real project. Whether the future the marketing promises is the future the infrastructure can deliver.

I don't have answers to most of those questions. I have observations, some intuitions, and a lot of personal evidence from work I did with my own hands. I tried to be honest about all of it — the parts I'm confident about, the parts I'm uncertain about, the parts where I changed my mind partway through, and the parts where I'm still working it out.

Who It's For

I also tried to listen to people whose perspectives I don't share. Some of them I came to agree with. Some of them I still don't. But I think the conversation about AI right now is dominated by a small number of voices with a financial interest in a particular outcome, and the people most affected by what's coming — the experienced practitioners with families and mortgages and careers built over decades — deserve more than anxiety and a subscription link.

This book is my attempt at a different kind of conversation. Quieter, slower, grounded in what I actually saw. Written for the person who wants to think honestly about what's happening rather than be sold on what to do about it.

How to Read It

If you came here looking for a methodology guide, you'll find one. The framework is in chapter two. The case studies in chapters three through seven show it in action across very different kinds of projects — from a SaaS platform built from a brain dump to a federal application demonstrated live to government stakeholders. The patterns are real and they're transferable. You can read those chapters as practical reference material and walk away with something useful.

But if you read straight through, you're going to get something else too. You're going to follow me through a year of discovery, doubt, exhaustion, fascination, and quiet hope. You're going to see what it looks like to find work meaningful again after years of not noticing it had stopped being meaningful. You're going to read the questions I'm still wrestling with about where this all leads. And if you've been doing this kind of work for as long as I have, you might recognize yourself in some of it.

That recognition was what surprised me most about writing this book. The methodology was always going to be useful to someone. The journey turned out to matter more.

Welcome to it.