First light, wherever you are
Full-stack software developer
I build practical software across interfaces, services, data, and delivery. I would rather own a feature end to end than hand it over a wall.
Accessible, fast front ends built with the web platform first. The empty state and keyboard path matter as much as the happy path.
Clear HTTP and event-driven contracts, boring deploys, and logs that answer the question someone is actually asking.
Schemas, migrations, and queries designed for the people who will maintain them after the launch week is over.
CI, infrastructure, preview environments, and the small scripts that return an hour to the team every week.
5 shown · arrow keys move between projects.
Scheduling for marine service yards
Boat yards were booking haul-outs on whiteboards and losing a day a week to double bookings.
Invoice reconciliation service
Finance teams were matching payments to invoices by hand after a nightly batch missed ambiguous records.
Offline-first inspection app
Inspectors worked without reliable signal and re-entered notes when they returned to the office.
A migration linter for Postgres
A safe-looking schema change locked a production table during checkout traffic.
Design system and component library
Six product teams had six visual languages and different keyboard behavior for the same controls.
Good systems rarely arrive all at once. They grow through patient observation, smaller decisions, and the care to leave the next person a clear path.
Replace this sample entry with team size, scope, and one result with a unit and baseline.
Describe what you owned, how you worked with others, and what became measurably better.
Keep this to one or two lines. Mention mentoring, on-call responsibility, or delivery scope when true.
Guardrails work when they explain the risk and leave room for an informed exception.
Connectivity changes what a product can promise, not merely how its database catches up.
A release should be observable, reversible, and small enough to understand under pressure.
Most awkward code is a fossil of a real constraint, deadline, or missing tool.
If the work here overlaps with a problem you are solving, email is the best place to start.
hello@liamshermanparris.ca 
