Writing // Archive
A growing collection of writings on architecture, frontend craft, and team practices.
"Astro is for content sites — why would you put Clean Architecture in it?" Because the moment your in-memory data becomes a real API, the question stops being rhetorical. Here's how this very portfolio layers presentation, domain, and data so the framework stays a replaceable detail and the business rules never learn it's Astro at all.
A UI testing strategy that survives refactors: test from the user's side, treat presentation hooks as implementation detail, and only test hooks in isolation when they're genuinely reusable utilities. Less fragile tests, fewer rewrites, more confidence.
The discourse keeps asking the wrong question. 'Will AI replace programmers?' is a coin flip dressed up as analysis. The honest question is which kind of programmer — and the answer is uncomfortable for one half of the industry, liberating for the other.
Native nesting closed most of the gap that made preprocessors mandatory. Most — not all. A practical guide to what's good, what's still missing, when to drop Sass or Less, when to keep them, and how to keep your stylesheets honest with Stylelint.
Some Entities cannot live alone. They only make sense inside a cluster, governed by a single 'super Entity' called the Aggregate Root. A practical, opinionated guide to consistency boundaries, invariants, and the rules that keep your domain from rotting.
Two of the smallest building blocks in Domain-Driven Design — and the ones engineers most often get wrong. A deep, practical guide to identity, equality, immutability, and how to decide which one to reach for.
Showing 6 of 6 articles