Each one below states the problem, the decision that mattered, and what it produced.
2
React Native builds, shipped on Expo.
5
Full-stack sites and platform migrations.
3
Agent pipelines in the product, and builds where AI authors the work.
4
Three.js — WebGL, scenes, shaders, animation.
Web
Moved a live React 16 tourism platform onto Next.js without a freeze window.
runtime crashes
~5-6% down
Crash handling added across the application.
REST endpoints integrated
4+
Each one hardened with defensive validation and error handling.
downtime
None
The legacy app kept serving traffic through every step.
Web
A headless CMS backend serving structured, multi-language government content over a custom REST API.
custom document types
10+
Each one modelling a content shape editors fill in without touching a developer.
Web · Mobile
One Umbraco backend and one set of API contracts serving both a web platform and a React Native app.
Web · AI-First
This site. One Zod schema feeding the build, a serverless API, and a CLI that authors the content.
checks per commit
5
Lint, format, typecheck, Vitest, and a production build. All five stay green.
schema definitions
1
The same Zod schema validates the CLI, the build, and the API request bodies.
Web
A distributed store for sensor readings, with the partitioning logic written in PL/pgSQL.