Posts
-
HTML-first or SPA: Reset the Default, Skip the Holy War
The test is where state lives and whether interaction swaps content or drives local state; default to HTML-first and upgrade to the client only when you must
-
A Thin BFF with Fastify
BFF layers don't need to be heavy — Fastify v5's schema-driven design is enough to hold the boundary
-
BFF Still Earns Its Keep in 2025 — It Was Never a Trend
A BFF is not a fashionable layer. It is where you make plain who faces the browser, who faces the backend, and who carries the risk.
-
Interactions as HTTP: What htmx Gets Right
htmx reduces interactivity to request/response, keeps state on the server, and asks whether you actually needed a SPA in the first place
-
Markup First: Describe the Structure, Then the Behaviour
Rather than starting from framework components, describe the structure in HTML first and let behaviour be a thin layer on top.
-
Goroutines and Channels
Share memory by communicating, and where that principle stops applying.
-
ClickHouse Basics: MergeTree and Tiered Storage with S3
Getting started with ClickHouse, the interesting bits of MergeTree, and hot/warm/cold tiering onto AWS S3 — with a Docker quick start.