Available for new work · Burlington, Ontario · --:-- local
I'm an independent engineer building full-stack web apps, interfaces, and internal tools. No deck-ware, no buzzwords — the demos below run live on this page. Read the code, then judge for yourself.
01 — Live work
Four things I built, embedded and fully interactive — three small tools and one full product. Nothing here is a screenshot. Click around — this is how I'd build the real thing for you.
Demo 01 · decision logic + UX
One small state-machine engine, configured for two very different sample businesses — a café and a SaaS app — each with a customer and an employee flow. Pick a business, pick who's asking, and walk the menus. There's a Back and a Main menu button at every step, so you can never get stuck. No framework, no backend.
Demo 02 · real-time calc + formatting
A tool for closing out a till. Enter quantities per denomination and totals roll up with eased animation, formatted in CAD, columns aligned with tabular figures. The kind of small, correct utility internal teams actually use.
Bills
$0.00
Coins
$0.00
Total
$0.00
Demo 03 · parsing + state
Paste raw JSON, get it parsed, validated, and pretty-printed instantly — with a clear error pointer when it's malformed. A throwaway utility that shows how I handle input parsing, error states, and tight feedback loops.
Demo 04 · Zebbly · kids + parents
A real product I built and shipped as Zebbly: a math-practice app a child actually wants to open, with a private grown-ups side for monitoring and control. Each day lights up one subject; ten-question sets and a 60-second Speed Game earn stars. The parent view turns all of that into a report card — no spreadsheets, no nagging.
Try it live
A build-your-own web radio. Drop in your own MP3s and they play instantly — full player, visualizer, and EQ — entirely in your browser, nothing uploaded to a server.
02 — Capabilities
Plainly stated. If it's not on this list, I'll tell you and point you to someone who's better at it.
Full-stack web apps and APIs. Readable, tested code and a project structure the next person can pick up without a tour.
Interfaces that are clear before they're clever. Accessible, responsive, and consistent — design systems that engineering will actually keep using.
Scoping, shipping, and clear communication. I'd rather send you a working build on Friday than a status update.
03 — How I work
You send a brief. I come back with a concrete plan, honest trade-offs, and a fixed first milestone — not an open-ended retainer.
You see real, working increments early and often. No big-bang reveal at the end, no surprises on either side.
It goes live, documented, and maintainable. You own the code. If you want me to stick around, that's your call — not a default.
04 — Contact
A couple of lines about what you're working on is plenty to start. I read every message and reply directly — usually same business day.