A short philosophical piece I've been sitting with: 'The Art of Starting Over.'

It's close to something I keep coming back to — that being authentic matters more than achieving. Most of what we call starting over is really just permission to be honest about what we want next.

Watch below.

Built this as a satire and ended up with a real app.

A polished, gamified wellness-app experience — daily check-ins, streaks, 'progress' charts — pointed at the most chaotic possible use case. The satire is the framing; the app is genuinely functional underneath.

Walkthrough below.

A small win from my last role I keep coming back to: we took a key Primewell Marketing Portal workflow from ~15 second response times down to under 2 seconds — about a 10× improvement.

No service rewrite, no caching layer added. Just a careful pass through the SQL Server execution plans, three new indexes on the right columns, and one query rewrite to remove a hidden N+1.

Lesson I'd share: before reaching for the bigger hammer, read the plan. The bottleneck is almost never where you think it is.

Shipped my new portfolio site this weekend after putting it off for far too long.

Stack: Astro + a single content.json file. No CMS, no database, no backend. Deploys to Vercel in seconds, edits at 11pm in a text editor.

Sometimes the simplest stack really is the right one. Open to feedback — link in the first comment.

One of the most underrated things you can do as an engineer is document the systems no one else wants to touch.

During an org restructuring at BCBS I spent a few weeks reverse-engineering and writing up three enterprise portals — Member, Broker, Provider — across frontend, backend, databases, deployments, logging, and external integrations. Nobody asked. It made onboarding faster, debugging cheaper, and ownership clearer for the whole team.

Writing it up here.