Product engineer, frontend, backend, dashboards, mobile and the infrastructure under it, without a team to coordinate.
A prototype or a spec becomes a launched product.
Ongoing feature work after handover.
An inherited or stalled codebase reaches production.
A full rewrite. If that is the answer, I will say so first.
Ongoing product engineering as an embedded pair of hands.
On-call. I am not a rota.
Independent product work, never client work, shipped between October 2025 and July 2026. Every one was scoped, built, released and is still maintained by one person.
I use AI heavily and verify everything. Tests, review and monitoring before anything ships.
We define the outcome, constraints and what does not need to be built now.
I turn the work into a technical approach and a practical order of operations.
Each week ends with progress you can see, test and use to make the next decision.
We release carefully, leave clear operating notes and make the product ready for its next owner.
20 posts across 7 topics
A Rails engine should be extracted only after its boundary has survived production work. The Responsa case shows what moves out, what stays, and why now.
Which AI automations are worth paying for, when a scheduled job or scoring rule is better, and what evals, drift and review really cost in production.
When structured design work saves a build, when it delays learning, and which product decisions must happen before code can honestly begin in a real product.
2 to 3 days per week, from August 2026
Email is the fastest way to reach me. I reply within two working days with the practical next step, not a discovery call.