Stack & engineering

The technical record of how this ecosystem is built. The stack is deliberately locked and narrow (one framework, one styling approach, content as typed code rather than a CMS) because a solo operation cannot afford the tax of maintaining variety across nine apps.

Content-as-code is the decision with the longest reach, and several articles work through its consequences. When every article, tutorial, and app statistic is a typed TypeScript object, a broken internal link, a missing image, or a renamed app becomes a compile error rather than a support ticket. The cost is that content edits go through a build; the benefit is that content cannot silently rot.

The AI-assisted engineering material is written from production experience rather than demos: where frontier models genuinely compress the work, where the review burden eats the gain, and what has to be true of a codebase before either is possible.