Engineering leadership
Technical direction, delivery discipline, and standards teams can work with.
Engineering leader and founder.
I build products and technical systems, and I lead the work needed to get them shipped.

I have worked across software, operations, and product delivery, with a strong bias for practical execution. I care about technical quality, clear tradeoffs, and making the work matter.
Technical direction, delivery discipline, and standards teams can work with.
Product choices shaped by business pressure and limited time.
Public tools and notes pulled from real engineering work.
Reliability, data, evaluation, and the product systems around them.
Proof
A short view of the products, systems, and public work I tend to take on.
Public work
Technical notes and open-source projects from practical engineering work.
Rails
Service objects are useful when they make a boundary clearer. They become noise when they only move code without improving the system.
Technical Note
Global coverage numbers can hide the risk in the change under review. A branch-focused SimpleCov group makes review more concrete.
Engineering Practice
Commit messages preserve intent, tradeoffs, and operational memory. They are part of the engineering record, not administrative noise.
Open source
Generate sitemap indexes and child sitemaps from explicit Ruby definitions, keeping sitemap ownership predictable and reviewable.
Open source
PostgreSQL image with PgBackRest preinstalled, backup-ready defaults, and flexible configuration mounts for production database operations.
Open source
Convert GitHub pull requests into a single Markdown file for offline review, local AI workflows, and focused engineering handoffs.
If the work needs product judgment, technical depth, and steady execution, it is the kind of problem I like.