How I build.

I work across design, code, data and product. Knowing enough of each to connect them is my depth. AI takes that further. Four stops, each with something you can check.

Several disciplines.
One build.

Sitter is a recall app for fourth graders. One public repo holds its memory model, a phone interface for children and 109 tests.

Problem first.
Tool second.

The problem is text you can read. The 3D scene is the tool. If it fails to load, or you reduce motion, you get the same text without it.

AI output
is a proposal.

I remain responsible for the decision. Every push to Sitter runs a syntax check, 109 tests and a content check.

One core.
Three apps.

Sitter’s scheduler drives three apps: the student app, a family game and a practice pilot. They share one file.

01

Code

Read Sitter’s source. MIT, no dependencies.

02

Tests

Clone it and run npm test.

03

App

Try Sitter on a phone. No login.

What are you
building?

Tell me about your team and the problem you want to solve.