This was the last note on the list, and I didn’t plan it that way.
When I sat down and wrote out a handful of topics—things I’d worked on, circled back to, abandoned, revived—this one quietly ended up at the bottom. Creating a book. Uploading it. Hitting publish. I didn’t consciously save it for last, but looking back, it makes sense.
Because this is the point where everything else converges.
On December 31, 2025, I uploaded my first book to Amazon KDP: Sudoku Gauntlet. It was the first time something I’d built—slowly, imperfectly, and over years—crossed from “in progress” into “exists.”
Not finished.
Not optimized.
Not proven.
But real.
The decision to publish didn’t feel dramatic in the moment. There was no celebration, no big reveal. It was mostly a checklist: files uploaded, metadata filled out, pricing set, proof ordered. Very procedural. Almost anticlimactic.
And yet, once it was done, something shifted.
Up until that point, everything lived in preparation mode. Tools. Scripts. Ideas. Systems. All necessary, but all internal. Publishing changed that. It introduced an imaginary finish line—the kind you don’t notice until you cross it. Not because the race is over, but because now you’re undeniably in it.
There’s still distance ahead. More books. Better covers. Stronger positioning. A series to build out. None of that disappears just because the first one is live. But publishing marked the transition from working toward something to participating.
After uploading the book, another decision followed almost immediately.
Originally, I thought I might keep things simple and focus only on KDP—skip the website, skip email, reduce surface area. But publishing made it clear that the book wasn’t the endpoint. It was the anchor. The thing everything else could finally connect to.
So I returned to the website.
I returned to email.
I returned to thinking in terms of a broader ecosystem again.
Not because it was required—but because now it made sense.
There’s also something humbling about seeing your work in the wild. Once it’s uploaded, it’s no longer theoretical. It can be bought. Judged. Ignored. Reviewed. That’s uncomfortable, but it’s also clarifying. It forces a shift from perfectionism to iteration.
This wasn’t about “launching big.”
It wasn’t about hitting numbers.
It wasn’t even about validation.
It was about closing a loop that had been open for years.
An idea became a thing.
A system produced an output.
Preparation gave way to action.
The marathon isn’t over. There’s still plenty of race left to run. But that first step across the line matters. And now that it’s been crossed, there’s no pretending otherwise.
That’s what publishing this book really represented.
Not the end —
but the moment the work became real.
