Skip to content

colophon

How this site is made

The fourth version. The source is on GitHub.

  1. 2026-10v3warm paper, ASCII figures, a monorepo← you are here
  2. 2026-06v2.5warm paper, a game, an animated mascot
  3. 2026-03v2minimal, white, a list of projects
  4. 2024-09v1MS-DOS terminal, a Commodore 64 in the hero
Diagrams
Every figure is plain text: the box-drawing I already use in READMEs. A small parser in packages/ascii finds the boxes, traces the lines between them, and treats arrowheads as one-way so two parallel lines stay two paths. The renderer lights a path and steps a packet down it, one character at a time. Tests check that every figure on the site names boxes that exist and lines that are drawn.
Type
Newsreader by Production Type for reading. Monaspace Xenon and Radon by GitHub Next for diagrams and margin notes: subset, renamed per their licence, and kept whole for box-drawing glyphs that the usual web subsets drop.
Colour
Khadi paper. Neel, indigo, for the things in a system; kesari, saffron and my surname, for what moves through them. Kept that way on purpose: cream, a rust accent and a big italic serif are what generated sites default to this year.
Motion
Slow on purpose. A long, soft scroll (Lenis), things that print rather than pop, CSS scroll-driven animations and view transitions where the browser supports them. Ask your system for reduced motion and almost all of it stops.
Stack
Turborepo and pnpm; Vite, React 19, TanStack Router and Query, Tailwind CSS 4, cmdk, Lenis. Animations are CSS wherever they can be; the packets and the slow scroll are a little JavaScript. Hosted on Vercel.
Tracking
None. No analytics, no cookies, no third-party scripts, and no third-party requests from your browser: the GitHub numbers are fetched when the site is built.
For machines
/llms.txt and a JSON résumé, generated from the same content as these pages.
Keys
⌘K or ctrl+K for everything · t for the tl;dr · z to let the page doze off.
Built with
Claude Code. I set the direction, the taste and the rules; Claude ran the research pass and wrote much of the code. Every number about my work was checked against the repository it came from before it went up. And the sentences are mine to answer for.

Sites that taught me something

Before this rebuild, a research pass with Claude read 257 personal sites: people at AI labs, design engineers, people who explain systems for a living, builders here in India. These 30 changed something on this one. What I took from each, in one line:

At AI labs

  • Chris OlahA legend before the mechanics, then one part lit per figure. Every figure here steps that way.
  • Adam PearceProse asks, the figure answers, the prose interprets: the order each replay follows.
  • Andrej KarpathyOne dry aside on an austere page is enough. See the bottom of the receipt.
  • Tristan HumeA log of everything, from the first crappy website on. The git graph of my path is the same idea.
  • Thariq ShihiparAn honest status on every project. The local agent says prototype, because it is one.
  • Ilan BigioLeave something in the console for whoever opens it.
  • AI Futures ProjectA figure that stays put while the story moves. The replay's diagram holds still as the trace plays.
  • Peter SteinbergerA clean, agent-readable twin of the site. Here: llms.txt and a Markdown résumé.

Explaining systems

  • Bartosz CiechanowskiBuild the system from nothing and let the reader drive. The replays run at your speed, or not at all.
  • Sam RoseRequests you can watch move: the packets walking the figures.
  • Bret VictorReactive documents: pick a different moment, and the figure and the prose change together.
  • Chip HuyenOne architecture, drawn up a box at a time.
  • Thorsten BallAn agent is a loop, some tools and a way to stop. Fig. 1 starts there.
  • Julia EvansPlain words for hard systems, and a handwritten note in the margin.
  • Simon WillisonWrite it down while it's fresh. The field notes are that habit, in public.

Craft and motion

  • Emil KowalskiAnything you touch answers in about 200 ms. The slowness is only where nothing waits on it.
  • Paco CourseyRadical restraint. And cmdk, the library under the ⌘K menu here.
  • Cyd StumpelNearly all the motion in plain CSS: scroll-driven animations and view transitions, no animation library.
  • darkroom.engineeringLenis, the slow scroll under every page.
  • Maggie AppletonNotes that say how finished they are. Mine say draft until they aren't.
  • Lynn FisherThe site's own history is part of the portfolio, hence the version list at the top of this page.

AI builders

  • Sebastian RaschkaAsk every system the same questions (motive, decisions, what was ruled out, what it doesn't fix), and the differences show.
  • Hamel HusainEvals as the spine. On the receipt, “eval” means a fixed graded set, same model and prompt.
  • Sander DielemanSay plainly where AI was involved in making the site.
  • Vicki BoykisA site that documents itself. This page.
  • Jeremy Howard · Answer.AIllms.txt: a clean index for models, generated here from the same content as the pages.
  • Matt WebbTime as material. A clock, a page that dozes off, a site that feels lived in.

Builders in India

  • Kailash NadhA quiet page that knows its own history.
  • Arpit BhayaniNotes titled as claims. “Unmeasured is not zero” is one.
  • S AnandWritten for people and for agents at once.