How this site was built
I tell people to build things with AI, so it seemed only fair to show my work. This site was planned, written and coded in conversation with an AI coding agent, and this page is the honest account of who did what.
What I did
I set the direction, chose the colors and typefaces, decided what belonged on which page, and pushed back when a draft missed the point. The first plan put my three best-known ideas on the home page, and I moved them into their own section because the home page should be about a person and not about a framework.
Every fact here traces back to something I have already said in public, whether in a talk, a podcast, my newsletter or my LinkedIn profile.
What the AI did
An AI coding agent working inside Cursor researched my public record, proposed the structure, drafted the copy from my own talks and essay, and wrote the code. I reviewed and edited as we went.
I asked for the copy and the design to avoid the habits that make a page feel machine-made, such as little labels perched above every heading, chopped-up sentences and rows of identical cards. You can decide how well that went.
What it is made of
The site runs on TanStack Start with React, TypeScript and Tailwind, and it is hosted on Lovable. Motion is handled by GSAP, with Lenis smoothing the scroll for people using a mouse or trackpad. The slow light in the header is a small shader, and the line that runs down the home page is a single drawn path.
Headings are set in Instrument Serif and everything else in Figtree. Both fonts are served from this site instead of a font service.
What it tries to respect
It was designed for a phone first. If your device asks for reduced motion, the animation switches off and every page still reads from top to bottom. The interactive pieces in the Ideas section keep what you type in your own browser and send it nowhere.
The photographs are mine, the pictures of builds are photos or screenshots of the real thing, and the rest is type and drawing done in code.