A little about me

The developer

I'm Keenan — a full-stack software engineer with 7+ years building web platforms and automation tools, mostly in healthcare. I've spent that time close to the hard parts: migrating legacy systems to modern APIs, building automation that runs across multiple hospital systems, and shipping internal tools that non-technical teams actually rely on.

I build production software in TypeScript, React, React Native, and Node. My split in recent positions has been roughly 20% frontend / 80% backend, but I'm comfortable in either arena. I care about keeping projects as clean as possible — through (actually helpful) logging, clear separation of concerns across the codebase, and real engineer ownership of the code that gets written and deployed.

Lately I work hand-in-hand with AI development tools: I architect the system, then direct AI to turn ideas into working software quickly without giving up code quality or test coverage. I'm based in Holland, Michigan and work remotely, and I'm currently looking for my next senior engineering role.

Safety Llama

The dog in the picture is Angus. He was a 170lb Dane/Mastiff with the gentlest soul a dog could have. The llama was his favorite toy, and he would run and grab it anytime he got excited or was feeling anxious. It was his safety blanket, and we called it his Safety Llama.

When I decided I wanted a brand for the side projects I was building to live under, it seemed to fit the bill.

What I'm building

Right now I'm building The Owner's Manual, a homeowner reference app directed toward DIYers. The app contains AI-powered lookups, affiliate commerce, and a full React Native mobile client. I designed the data model, the API is built on Node and Prisma, deployed to Railway, and the mobile app is built with Expo EAS. It's still a work in progress and currently in beta — not yet on the App Store or Google Play, but both are coming in the near future.

It began out of a personal frustration with always having to look up maintenance items that were infrequent enough that I'd never commit them to long-term memory. It was just a hassle, and I wanted a way to easily save that information and pull it up later. From there, the ideas and features kept growing.

If you want the professional story, the resume page has the full picture. If you want to talk & connect, the contact page is the place.