If the product isn't moving, move it yourself.
Founding Engineer / Staff-level ownership in a seed-stage environment.
Logs over excuses. Snapshots over references. Pre-bootup over post-mortem.
Transactions, triggers, and one-pass algorithms. Frameworks are rented; logic is owned.
A 1.5-hour Christmas SQL call. A 100 kg adrenaline season. A trigger that ended an era of silently lost rows.
The IPO Framework
01 / Input
Define the data.
What enters the system? Schema, source, frequency, failure mode. If you can't name it in one sentence, you haven't earned the function.
02 / Process
Transform the data.
Framework-agnostic. Pure logic where possible. Boring, deterministic, observable. The kind of code the on-call engineer in 2028 will thank you for.
03 / Data Context
Know the rows.
What does a duplicate look like? What does a soft-delete look like? Which fields are nullable in practice vs. only in the schema? This is where senior begins.
04 / Output
Deliver the artifact.
The thing the user holds at the end. If the output isn't traceable to the input through every line of process, the system is not in production yet.
Case Studies
- 01 The 1.5-Hour Christmas SQL Call — Dec 25, 2022 →
- 02 The 175-Lead Bug — silent SMS drop, the Metabase guardrail, ownership over attribution →
Deep Dives
- A Identity & Vibe — the IPO framework, the motto, the contract. →
- B The Logic-First Manifesto — six principles, one operating manual. →
- C The Engineering Odyssey (2020 — 2024) — phases, milestones, the trajectory. →
- D Technical Blueprints — Scheduling v1, the audit trigger, the polling pattern. →
- E Product & Growth Engineering — Lead Masking, Mixpanel + Intersection Observer, the PM-Engineer. →
- F Multi-View Mapping — same engineer, three zoom levels. →
- G The Main Log — the unvarnished archive. Names, dates, weight gain, arguments. →
Contact