NOVA FOUNDRY

Or improve the app you already have

• Customizable dashboards

  Widget layouts users can arrange and save, with panels that load and fail independently.

• Complex tables

  Sorting, filtering, grouping, column controls, and inline editing that stay fast as the data grows.

• Frontend workflows

  Multi-step forms, bulk actions, and review flows that keep state correct across reloads and slow networks.

• APIs behind the UI

  API design and implementation for the screens that depend on them, from server-side filtering and pagination to types shared between client and server.

Exploring a Caro-Kann line family on the board chessecho.com →

The problem

Opening prep is easy to study and easy to forget. Reading a line in a study doesn't mean you'll find the move at the board.

What I built

• Opening library organized by family, color, and difficulty
• Board-first study and drills for saved lines
• Spaced-repetition review queue, with intervals that stretch from 1 to 30 days as lines stick
• Recall tracking and progress trends
• Accounts, email flows, and Stripe billing

How it's built

• TypeScript
• React 19
• TanStack Start
• Turborepo
• Drizzle ORM
• Postgres (Neon)
• Better Auth
• Stripe
• Resend

Chess is the subject, but the engineering isn't chess-specific: a dense interactive UI, state driven by the server, and the auth, billing, and database layers underneath. It's the same kind of work I take on for clients.

How I work

Owned end to end.

Design, engineering, and operations stay in the same hands. Nothing gets handed off halfway through.

Evidence over fashion.

Boring where boring wins, new where new earns it. Every choice is one I can point back to.

Ship, then learn.

Nothing gets better until it's in real hands. I release early, watch closely, and iterate from there.