Colophon

A note on the thing you’re holding, since by now you’ve read enough of how I think to be owed an explanation of how this was made.

Why it exists. I didn’t want a portfolio. Portfolios answer what have you done, and I find that the least interesting thing about anyone. I wanted to answer how do you think — and the honest format for that is not a grid of projects. It’s a book you read slowly. So that’s what I built. If you’ve made it this far, it worked, and I’m grateful for your time, which is the only thing I actually asked for.

Why it was built this way. Everything you’ve experienced is an argument made twice — once in what it says, once in how it behaves. The calm, the space, the single quiet voice, the refusal to shout — those aren’t aesthetic preferences. They’re the same systems thinking from Chapter 04, pointed at your attention instead of a product. The medium had to practise what the writing preached, or none of it would be true.

The technologies used. Next.js and TypeScript for the structure. Tailwind for a token-driven visual system. MDX so the writing stays the source of truth — every chapter you’ve read is a markdown file, and the two reading modes are two layers of one document, not two themes.

The role AI played in building it. I’ll be plain, because the alternative would contradict Chapter 06.

Which is the last thing I want you to leave with, and the truest sentence in this book:

AI accelerated the execution. Human thinking created the direction.

That was the whole point. Thank you for reading.

❡