Skip to content

A working method · 2023–ongoing · Practitioner

ShippingwithAI

I don't need to speak a language if I have a translator — how knowing the theory deeply enough to judge right from wrong lets one product person both plan the system and build it. This site is exhibit A.

1
person planning and building
10 yrs
of theory doing the judging
This site
is the working example

01/Context

The generalist's dilemma

My career kept pulling me deeper into the engine: marketing into data, data into infrastructure, infrastructure into product. At every layer the pattern repeated — I understood how the thing should work before I could personally type out every line of it.

The conventional answer is: specialize, or hand off. Both lose something. Specialists lose the whole-system view; handoffs lose intent in translation.

02/Problem

Handoffs leak intent

Every translation between the person who decides and the person who builds costs fidelity. Requirements docs flatten nuance. Tickets strip context. The person closest to the customer problem is usually furthest from the keyboard where it gets solved.

I don't need to speak a language if I have a translator.

03/Approach

Theory is the job. Typing is not.

AI collapsed the distance between deciding and building — but only if you can judge the output. That's the actual skill: knowing dimensional modeling well enough to catch a wrong join, knowing design systems well enough to reject a lazy layout, knowing web performance well enough to ask where the bytes went.

  • 01Learn the theory for real. AI amplifies judgment; it can't replace it.
  • 02Direct like an editor, not a passenger: tight briefs, ruthless review, taste as the filter.
  • 03Keep the invisible parts honest — naming, structure, semantics, speed — because that's where quality actually lives.

04/What I built

Exhibit A: the page you're reading

This site was planned and built this way — Next.js 16, typed content models, native view transitions, a design system in CSS variables, and an accessibility and metadata layer most visitors will never see. So was the Sploot warehouse. So were the lifecycle systems.

IntentBriefBuildaiJudgehumanShipnot right yet — again“i don’t need to speak a language if i have a translator”judgment compounds · syntax depreciates
The loop: intent → brief → build → judge → ship. The human owns both ends.

There's a switch in the navigation labeled “under the hood.” Flip it, and this site will annotate itself — every design and engineering decision, explained in the margins. That's the method, made visible.

05/Outcomes

Speed with judgment

One person who can hold the customer problem, the system design, and the build in the same head — and ship all three without a handoff. That's not a workaround for a missing team. Increasingly, it's how the best small teams work, and it's the operating system underneath everything else on this site.

Next case study

One source of truthSploot Veterinary CareFour tools, one warehouse, zero arguments about the numbers.