Selected work — curated, not a repository dump

Work worth keeping.

A short list. Independent software I ship myself, the professional problems that shaped how I build, and a few small tools.

Independent software

3 projects · signed or public source

Cursor total included23%

Claude 5-hour100%

Codex 5-hour12%

SettingsAI Usage MeterQuit
01 · macOS · iPhone · WatchShipping

AI Meter

See Cursor, Claude Code, and Codex usage without living in three dashboards. A local-first meter for included pools, rolling windows, spend, and on-demand.

Status
Signed and notarized Mac builds on GitHub Releases. iPhone and Watch stay on TestFlight.
For
People who use more than one of these tools and want a glanceable answer to "where am I?"
Choice
Credentials stay in the device Keychain. The meter reads local sessions. It does not send them to a backend I run, store tokens in iCloud, or hand credentials to the Watch.
02 · macOS 14+ · Apple siliconShipping

CursorStack

All those Cursor windows, one manageable workspace. A tab strip over the real windows, rather than another editor.

Status
Signed and notarized Mac builds on GitHub Releases. Apple silicon, macOS 14 or newer.
For
People who keep several Cursor projects open and want to move between them without hunting windows.
Choice
macOS Accessibility moves, resizes, and focuses the original Cursor windows. CursorStack does not embed Cursor, read source, or upload anything.
03 · iPhone · Watch · MacPublic source

Daily On Plan

A daily nutrition sheet for iPhone, Apple Watch, and Mac. Protein toward a goal, hydration, and whether you followed the plan. Not a service, and not a medical device.

Status
Public source. The README does not establish a public App Store release.
For
Someone who wants one day, written down, without an account or a community attached to it.
Choice
On the device by default. Optional iCloud sync for the journal. No account, and no backend of mine. iCloud is still a cloud feature.

AI Meter and CursorStack are independent projects. They are not affiliated with the companies behind the tools they sit beside.

Professional experience

Automotive is the deepest proof. Not the boundary.

I have built for both sides of the industry. Dealerships, where new cars are sold and serviced, and the independent repair shops of the aftermarket. They run on different systems, pressures, and people, and working across both taught me to respect the workflow, integrate carefully, and build for the busy day.

Current · Aftermarket repairSite

Shift Automotive

Principal Engineer

After years leading teams and operations, I chose a principal role to get closer to the building again. It puts me where the architecture and the code are decided, which is where I can drive the most change and help the whole team succeed. At Shift that means software for independent repair shops, where advisors, technicians, and owners need systems that reflect how work actually happens. I connect product decisions to architecture and implementation, and make sure the engineering holds up in production.

Previously · Dealerships

Volie

Senior Software Engineer, then Director of Engineering

Volie took me to the dealership side of automotive, where new cars are sold and serviced. I built software and integrations for dealership communications and, later, led engineering. Dealerships run on different systems, volumes, and pressures than an independent shop, and seeing both sides shaped how I build. Reliable external integrations, clear ownership, good delivery, and systems that support the people doing the work.

Previously · Aftermarket repair

Bolt On Technology

Developer, then Senior Vice President of Technology Operations

This is where I learned the independent aftermarket. I started as a developer on shop-management software for repair shops, building web applications and keeping the incoming data pipeline healthy across clients. The role grew into operations, support, customer success, and leading the development team, and then into technology operations after the company merged with Bolt On Technology. The work was bringing the journey together from pre-sales to post-sales, and building the teams and processes behind it.

Small tools

Things that remove an everyday annoyance

On the bench

Made for my own problems, still being polished

Each of these started as a problem I kept running into. I use them, they are still being polished, and they are not public yet. Source links go here when they are.

I still get excited about a good problem.

If you're building something thoughtful, working through a tricky engineering challenge, or trying one of my tools, I'd enjoy hearing about it.