Writing about the decisions behind the build
Technical notes on product engineering, system design, and the lessons that follow shipping real software.
How I Made a Public Portfolio Discoverable to Agents
Discovery for people stayed editorial. Discovery for agents became signed DNS, well-known catalogs, and honest auth metadata—without inventing a commerce protocol the site does not run.
- Agent Discovery
- DNSSEC
- Next.js
- SEO
How I Turned Cloudflare Analytics Into a Public Portfolio Feature
How I exposed aggregate Cloudflare traffic and field performance through a server-only Next.js boundary, then shaped it into a privacy-conscious dashboard with global reach, clear chart semantics, and country-level interaction.
- Cloudflare
- Next.js
- Data Visualization
- Web Vitals
How I Cut Key Interaction Latency by Up to 53%
Tracing the full click-to-database path exposed duplicate auth, extra queries, and UI waits—then measurement proved what improved.
- Performance
- Supabase
- PostgreSQL
- Optimistic UI
How I Cut Initial JavaScript Without Cutting Features
A measured Next.js performance pass that moved optional code out of initial routes and added budgets to keep the improvements from regressing.
- Next.js
- Turbopack
- Bundle Analysis
- Web Performance
The CMS Behind My Portfolio: From Edit to Public Page
How one content record moves through capability-gated Admin editing, shared contracts, Supabase RLS, and the public Portfolio renderer.
- Content Management
- Supabase
- PostgreSQL
- Next.js
How I Split One Next.js App into Four Products
The architecture decisions that separated Portfolio, Studio, Admin, and Auth while keeping shared contracts and one clear data model.
- Architecture
- Next.js
- Monorepo
- System Design
What Product Ownership Looks Like in Practice
Six decisions that turn a feature into a dependable product: problem, trust, data, experience, failure handling, and operations.
- Product Ownership
- Full Stack
- System Design
- Delivery
Why I Build Beyond the Ticket
How field work, full-stack engineering, and independent products shaped the way I think about complete systems—not isolated features.
- Journey
- Product Engineering
- Independent Work