// writing
Notes on building software well — architecture, reliability, and the non-code parts that make projects succeed.
A single model told to play three advisors just performs a debate with itself, and it always converges on a tidy consensus. Real dissent has to be enforced in the architecture. Here is how Camelot wraps a stateful, opinionated AI meeting around a deterministic core.
An LLM can turn a sentence into a trading strategy. The hard part is the boundary, making sure what it produces is valid, reproducible, and safe to run before any of it touches the engine.
Moving from PHP and WordPress to a TypeScript, React, and Next.js stack felt like a bigger jump than it was. Most of what mattered carried straight over.
A national health program needed content in several languages, an LMS, and a way to find care nearby, on one platform, stable enough for millions of visitors. Here is how it was structured.
Becoming a tech lead does not have to mean becoming a full-time reviewer of other people's work. Here is how I stayed in the code while keeping a team on schedule.
When lockdown hit, a client wanted to give people a free way to keep learning. Here is how I turned a WooCommerce store into a lending library without rebuilding it.