How we build production software. Every pattern, convention, and decision — from database queries to component architecture — distilled from real projects.
Tech stack selection, project philosophy, and the principles behind every decision.
Database standards, repository patterns, server actions, and data fetching strategies.
Route colocation, caching, multi-tenant isolation, and webhook design.
Files live next to the route that uses them
Building webhooks that never lose events
RLS: the database does the auth checking
How we think about cache invalidation
Testing strategy, TypeScript strict mode, CI pipelines, and incident response.
5-second CI that catches everything
What we test and why — confidence over coverage
Zero any, generated types, strict mode always on
Factories, mocking, and integration tests that prove it works
Systematic route audits that find dead code, wrong abstractions, and missing tests
When things break: our runbook
AI-assisted reviews that teach, not just gatekeep -- seven dimensions, three severities, zero ambiguity
Row-level security, input validation, security headers, and data lifecycle.
Zod schemas at every boundary
Defense in depth for multi-tenant SaaS
Row Level Security as your authorization layer
Retention, rotation, and responsible deletion
CSP, CORS, and webhook signature verification
Structured logging, error tracking, performance monitoring, and webhook observability.
Agentic development, decision velocity, documentation, and project scoping.
Think before you code — 2-3 approaches, then decide
User stories, architecture context, sub-task breakdown
CI passes first, then a rich description with test plan
How we estimate and ship on time
One-way doors vs two-way doors
Three-layer docs for humans + AI
Building with AI agents, not against them
The user should never wait
Component architecture, design standards, performance patterns, and internal tools.
Composition over configuration
Suspense, streaming, and instant UI
shadcn/ui, semantic tokens, premium by default
Data density over visual impact, scannability first