Profile · Web development desk
One developer, full stack — from requirements to ship date
Senior full-stack engineer, five years in. One TypeScript codebase, shipped to iOS, Android, and the web — with everything underneath it owned too.
Written by the subject, who also built the paperAndover · 3 min read
I work remotely from Andover, in TypeScript throughout — React and Expo at the front, Node, Apollo GraphQL and Next.js behind it, AWS underneath. Five years of it.
I hold professional-level AWS certifications in architecture and DevOps, which mostly means I'm the one who reads the bill.
The thing I do that most people don't is ship one codebase to iOS, Android, and the web and have it feel right on all three. That comes with the rest of it: release pipelines, over-the-air updates, App Store compliance, real-time data, and the CI that keeps it all moving. I've launched in regulated markets, and I've built and run a product entirely on my own, so I know what the whole job costs.
Evenings are for content systems. Payload CMS, mostly — Next.js in front of it, deployed on OpenNext, built so the people who own the words don't have to ask a developer every time they want to change one.
Enough of that repeated itself that I started publishing the pieces. The plugins are on npm, written because I needed them and couldn't find them, maintained in the open ever since — issues, releases, and the occasional breaking change, all after hours.
Open source has been the most useful thing I've done for my own work. It forces decisions you can defend in public, and it means the second client gets in a day what the first one waited a fortnight for.
Everything below is live, or was. The work is picked rather than padded and the experience is in order. If you're hiring, the CV is at the top. If you need something built, the address at the bottom is the whole system — I take on a small number of projects at a time and I'm honest about which ones I can do well.
