Seven years of building, in the order it happened. Engineering first, product because someone had to hold the vision, and a long habit of learning in public.

Engineering

An outstanding site is not only how it looks — it is whether it works, and whether anyone can find their way around it. I am comfortable in the awkward technical middle of a project: the part where the design is decided, the data is messy, and someone has to make the two meet.

See the work →

Product

I am not a product manager, but research, design and coordination are part of how I work rather than someone else's job. On Reperem they had to be — there was nobody else. That is the experience I bring to a team that already has a PM: I can hold the vision without needing to own it.

Reperem, end to end →

How it happened

  1. 2017—18

    Human-Centered Design 101Acumen

    A hands-on course that pushed me out of the chair to test ideas on actual people. Still the reason I start with the user rather than the schema.

    Foundation
  2. 2017—21

    Senior Software Engineer INoukod

    The first engineering seat, four years of it: Rails APIs redesigned for speed, a CSV/XLS uploader that turned spreadsheets into graphs on PostgreSQL, and releases automated through CI/CD.

    Work
  3. 2019

    Data Structures and AlgorithmsUdemy

    Closing the gap self-taught engineers tend to carry: Big-O, and knowing which structure to reach for before writing the loop.

    Craft
  4. 2019

    Adaptive LeadershipedX

    A Harvard Kennedy School framework for leading change when there is no easy answer. I have used it more than I expected to.

    Team
  5. 2020

    Learning to LearnUdemy

    Study and recall strategies with research behind them. Less glamorous than a framework, more useful than most.

    Craft
  6. 2021

    Reperem ships to the App Store

    Zero to one, alone: research, product decisions, React Native, Firebase, and the review queue. The first thing I built that people outside a repo depend on.

    Shipped
  7. 2021—22

    Full Stack DeveloperBairesDev

    Rails on PostgreSQL for a distributed team: data retrieval 25% faster, Jenkins CI/CD cutting release cycles by 40%, RSpec throughout, and a Next.js/NestJS monorepo held together with tRPC.

    Work
  8. 2022—25

    Web DeveloperMobile Pushers

    Rails applications plus the Node.js edge in front of them: Sidekiq for background jobs, NGINX load-balancing dozens of Node instances, Express auth middleware, and 100% on-time delivery.

    Work
  9. 2025—Now

    Full Stack DeveloperBioCollections WorldWide

    Healthcare data, end to end: C# services moving 10,000+ HL7/LIS medical records a month into a NestJS backend and MSSQL, a production AI chatbot on a Qwen model, and the legacy ASP Classic that preceded it all.

    Work
  10. Now

    Still learning, out loud

    Whatever I have had to work out the hard way ends up written down eventually.

    Ongoing

Off screen

Manga, long games, and music loud enough to be a problem for the people I live with. If you want to argue about any of those, write to me.