Skip to main content
BM

Ben Morrison

Full Stack Software Engineer

I left a pharmaceutical sciences PhD to build software, and I still bring a researcher's rigor to everything I ship. I typically work in TypeScript, React and Node, or whatever stack the team uses, with a focus on:

  • ETL pipelines
  • Design systems and components
  • Accessible, responsive interfaces
  • AI developer tooling
Want to connect?

What I build

  • Experience

    My professional experience and highlights of the work I've shipped.

  • Design System

    An example component library built on design tokens: easy to use, strict by design and fully themeable, with live docs and a theme creator.

How I develop

  • Bias for action

    When I hit a blocker and the next step is a two-way door, I take it. What I learn and the head start I gain are worth the time it might cost to undo.

    In practice

    When an external team stalled our role-access ETL pipeline even after approvals, I kept it moving by pulling the data by hand from an admin site we already had access to.

  • Ownership

    I'm responsible for the code I write, even after it ships. When something breaks, I want to fix it, whether or not it's still in my hands.

    In practice

    After our SDK and CLI toolkit for Kiro and Claude was adopted company-wide and handed to another team, I stayed on as one of its core engineers.

  • Have opinions, hold them loosely

    The best results I've seen come from teams where everyone brings an opinion and stays open to discussion. I bring mine, and I change it when a better solution shows up.

    In practice

    I was sure our intake app had to ship as an Electron app for its dependencies, until a coworker found that switching to the company's internal AI model let us serve it on the web. We switched.