Open source tool
Dadbod Grip keeps database changes inside a familiar editing model.
Dadbod Grip stages each mutation and keeps the exact SQL visible until the user applies it.
Process
Four selected case studies, with their constraints, implementation details, tests, and visual checks.
Shipped at scale
Multiplayer physics across console, PC, and mobile.
I architected the networked backend for a Unity ragdoll sandbox where players, vehicles, joints, and physics objects needed to remain responsive under real network conditions. The game passed 50 million downloads.
Product in development
Native stays offline while the web build loads route-sized data on demand.
Theosis now splits delivery by platform: native keeps bundled SQLite and full offline behavior; the public web path removed database and WASM startup, emits immutable route-sized JSON, defers heavy reference routes, and enforces a 650 KB gzip entry cap.
Founding engineering
From a pre-seed Bubble prototype to the production platform used through Series A.
I joined as the sole frontend engineer, replaced the prototype with React and TypeScript, then expanded into Python and FastAPI performance, PostgreSQL migrations, AWS and Terraform, release automation, agent workflows, security controls, and production data.
Deep dive
How dadbod-grip.nvim stays inspectable
Case: dadbod-grip.nvim
Edit database tables without leaving Vim.
The core job is not “build a database client.” It is preserving editor flow while making mutations reviewable before execution.
Use the tools already carrying the hard parts.
Vim provides the interaction model. Dadbod owns connections. The database remains authoritative. New code earns its place only around the missing workflow.
Keep each mutation inspectable.
- ALTER TABLE users ADD last_seen_at TIMESTAMP;
+ ALTER TABLE users ADD last_seen_at TIMESTAMPTZ;
+ CREATE INDEX idx_users_last_seen_at
+ ON users (last_seen_at DESC);DecisionKeep changes staged until the SQL is reviewable.
Staged changesSQL previewSingle transaction
Exercise the change at the level users depend on.
Preview the SQL before execution. Apply the staged mutations inside one transaction. Verify database state after commit and after rollback.
PreviewApplyVerify state
Inspect the real interface.
Tables, diffs, floating SQL previews, focus order, and empty states are checked in Neovim. Screenshots support the review but do not replace interaction.