I build software for the people doing the actual work.

  • Full-stack developer
  • Toronto
  • Physics, anthropology

Open to full-time roles, Toronto or remote

A sorting floor, a body shop front desk, a design studio. I spend time where the work happens, write down how it really gets done, then build the tool that fits. React, Next.js, TypeScript, Supabase and the Claude API, shipped and in use.

An exploded stack of four plates. At the bottom, skids on a sorting floor. Above it, a clipboard of notes and two sticky notes. Above that, a phone with a three-row app. On top, a table and a bar chart. Labelled: go where the work is, write down what happens, build the smallest thing, keep the numbers honest. 01 Go where the work is 02 Write down what happens 03 Build the smallest thing 04 Keep the numbers honest

Work

Three tools, three places of work
01

Sortlog

Daily sorting reports and hours for a containment-sorting crew at IQ Automotive Services.

Read the case study
A skid of eight cartons on a pallet, with its supplier label pulled off and shown to the right inside a camera viewfinder. Callouts mark the part number, supplier and serial barcodes, and note that one photo is read in the browser and the skid is filed under its part. Part no. (P) CX418DMOAA02 Supplier (V) 000417220 Serial (S) 104882317 One photo Read in the browser Skid 7 of 12 Filed under its part
Where
A containment-sorting crew at a customer plant near Toronto. I work on this floor.
Before
One Excel workbook per part, filled in by hand at the end of every shift. Hours typed again into a separate sheet.
Now
Photograph the skid labels. The app reads the barcodes, files each skid under its part, works out everyone’s times and builds the reports in IQ’s own format.
Status
Used every shift since late September 2026
Built with
Next.js 16, Supabase, Barcode reading in the browser, Claude Haiku, ExcelJS, jsPDF
02

613 Automotive

Estimates, work orders, inspections and invoices for a collision and mechanical shop.

Read the case study
An exploded stack of three printed sheets for one job: an estimate at the bottom, a work order, and an invoice on top. A small block to the right labelled totals in whole cents sends a dashed arrow to the totals box on each sheet. Estimate Work order Invoice Totals Whole cents, one module
Where
The front desk and the bays of a body, paint and mechanical shop in Kingston, Ontario.
Before
No real paperwork. Sample estimates made in ChatGPT, totals worked out on a calculator.
Now
Check-in on one screen, a job from estimate to paid in one place, four printed documents, the inspection on a phone in the bay, and one-tap quick sales for walk-ins. I also redrew their logo into a brand for the app and paperwork.
Status
In live testing at the shop since October 2026, changing with their feedback
Built with
Next.js 16, Supabase, jsPDF, Tailwind 4, Vitest, NHTSA VIN decoder
03

Amplifier

A reference library Claude scores, and a visual brief that finds what a client actually likes, not just what they say.

Read the case study
Two image cards standing side by side over a phone. The left card holds one open circle and is labelled quiet; the right card has the same layout with a filled, ringed circle and a block, labelled loud. One thing changes, the rest stays the same. On the phone the client picks which feels closer, about 20 pairs in 8 minutes. This Quiet That Loud One thing changes The rest stays the same Which feels closer? About 20 pairs, 8 minutes
Where
Amplifier, the small design studio I’m a partner in.
Before
A tagged reference library nobody kept up, and first meetings that started from a few adjectives and a guess.
Now
Clients spend about eight minutes choosing between images on their phone, from a private link or the studio’s site. The studio gets a prep page: what they’re asking for, where their words and picks really differ, and a starter moodboard.
Status
Rebuilt October 2026, in testing with the studio; the site in progress with Francis
Built with
Next.js 16, Supabase and pgvector, Claude Sonnet and the Batch API, Voyage multimodal embeddings, A Chrome extension

Also built

How I work

Four habits
  1. 01Go where the work is

    I work on the sorting floor Sortlog was built for, and I write the reports it replaced. For 613, I started from the paperwork they already had. The tool comes out of the place it will be used.

  2. 02Write down what actually happens

    Anthropology is mostly this: the gap between how a process is described and how people really do it. The workaround someone keeps on a sticky note is usually the feature.

  3. 03Build the smallest thing that removes the worst step

    Sortlog’s first version did one thing: turn the end-of-shift entry into the report. Skid tracking, times and the manager pages came later, once it was in daily use.

  4. 04Keep the numbers honest

    A physics habit. Money and hours are worked out in one place and tested against real samples. 613’s totals are checked against the shop’s own estimate. Sortlog’s Excel files keep live formulas, so a corrected number flows through.

Tools

What I reach for, and what I’ve shipped with
01Frontend
  • React
  • Next.js
  • TypeScript
  • Astro
  • Tailwind
  • Canvas API and Fabric.js
02Backend and data
  • Supabase: Postgres, auth, row-level security, storage
  • Node.js
  • SQL migrations tested in PGlite
03AI and automation
  • Claude API: vision, structured extraction
  • Gemini API
  • n8n pipelines
  • Instagram and Facebook publishing
04Paperwork and the floor
  • PDFs with jsPDF
  • Excel with live formulas (ExcelJS)
  • Barcode reading in the browser
  • Phone camera capture
05Deploy
  • Google Cloud (Associate Cloud Engineer)
  • Vercel
  • Netlify
  • Cloudflare
  • Git

I also built and ran a content pipeline in n8n that wrote, designed and published daily posts to Instagram and Facebook, with a canvas editor for last-minute fixes.

Hiring a full-stack developer?

I’m looking for a full-time role in Toronto or remote.
Email is the fastest way to reach me.

Or find me on LinkedIn and GitHub.