About · Edition I

I build things and put them where people can use them.

Sites, internal tools, systems that have to hold up when somebody is actually depending on them. Nothing on this site is a screenshot: every plate in the folio is running, and you are welcome to step inside and operate it.

The practice

Most of what I know came from selling before it came from building, and that order turns out to matter. Selling teaches you that nobody owes your work their attention — you earn the next ten seconds or you lose them. I build the way that lesson taught me to: every page has a job, every claim has a receipt, and the fastest path to the thing a visitor came for is the design.

I care less about whether an interface looks current and more about whether it moves someone toward the thing they came for. Fashion ages fast. A page that quietly does its job does not.

The portfolio itself follows the same rule. This shell is deliberately quiet — one typeface family speaking, one gold, a room kept dim so the work carries the light. The six systems it frames are the argument: a roofing site built for storm season, a reading surface where the typography is the interface, a page that repairs itself in front of you while you tamper with it.

Different problems, one habit: build the real thing, wire it up, and let people run it.

Principles

04

01

Operable over admirable

A screenshot proves nothing. Every entry in the folio is a running system you can step inside and use — if a visitor can't click it, it doesn't count. The work is the demo, and the demo is the work.

02

Restraint is the voice

One gold, used in maybe six places, and its power comes entirely from scarcity. The shell never raises its voice, because the moment it competes with the work inside it, both lose.

03

Robust is beautiful

The entrance here is pure CSS specifically so it cannot hang. Every effect degrades to plain, readable content on browsers and devices that don't support it. A cinematic site that occasionally strands someone on a black screen is worse than no cinema at all.

04

Evidence over adjectives

Claims carry numbers or they don't ship. If a system says it catches tampering, open devtools and tamper with it. If a page promises speed, measure it on a mid-range phone, not a spec sheet.

Process

03

I

Research

Current practice at build time, from primary sources — not trend listicles. What juries score, what buyers do, what actually converts.

II

Build

Whole surfaces, not patches. Real repos, typed content, version history. Design-critical work is built as real code end to end.

III

Prove

Run it on a real device. Test the keyboard path. Check the contrast arithmetic. Ship when it holds, and record what was decided so it stays decided.

Toolroom

  • Next.js 16
  • React 19
  • TypeScript
  • Tailwind 4
  • Base44
  • Vercel
  • Git

Design-critical surfaces are built as real code in real repos. Systems that genuinely need entities, auth, and relational data run on a platform that provides them. The tool follows the problem, never the other way around.

Now

MMXXVI

Edition I: this shell, and six systems moving from build to live. The folio is open — step inside.