How I build

Production discipline: typed end to end, tested against real infrastructure, shipped through automated gates.
TypeScript
Edge/Cloud
CI/CD
Type-safe

Typed end to end

One source of truth flows from schema to API to client. No drift, no hand-written contracts.Learn more →

Explicit error handling

Failures are typed and contextual at every layer, surfaced as actionable alerts, not buried stack traces.Learn more →

Clear architecture

Thin API layer, domain services, transactional orchestration with automatic rollback on failure.Learn more →

Real-infrastructure testing

We test against live services, not mocks — test suites in the four-figure range gate every deploy.Learn more →

Automated delivery

Every change passes lint, format, type-check, tests, and migrations before it ships. Staged promotion to production.Learn more →

Documented decisions

We chose Drizzle ORM over Prisma because the runtime executes V8, not Node — documented so the next maintainer inherits the reasoning, not just the result.Learn more →
Design
Type-safe contracts
Build
Test (real infra)
Automated gates
Staged deploy
Languages
TypeScript
GraphQL
SQL
Rust
Cloud
Cloudflare Workers
D1
R2
KV
Data
Drizzle ORM
SQLite/D1
Vector Search
Stripe
CI/CD
GitHub Actions
Vitest
ESLint
Drizzle Kit
This is how I built Tekel, Lucra's audited protocol, and a municipal RAG platform for local government.
See the work