How I Built a Static Site Generator in Go (and When You Should Too)
A hands-on account of writing a ~600-line Go static site generator for a data-driven site — the pieces, the pitfalls, and the honest build-vs-adopt decision.
Every review is written after real use. Every calculator shows the math. No recycled spec sheets.
A hands-on account of writing a ~600-line Go static site generator for a data-driven site — the pieces, the pitfalls, and the honest build-vs-adopt decision.
A Go CMS that is one executable plus a SQLite file. No PHP, no MySQL, no package soup — and what that does to deployment, security, and ops.
Every database incident I have caused traces back to skipping one of these steps. Stop, back up, work on a copy, verify, swap — the ritual that prevents disasters.
Behind the scenes of the /tools section: YAML definitions + a tested Go math engine + a JS mirror. Adding a new calculator is a config entry, not a code change.
One binary, one file, one cheap VPS: the honest full stack behind a Go + SQLite service — systemd, nginx, Cloudflare, backups, and what each piece is for.
What a CDN actually does for a content site, and the free-tier setup that caches assets, hides your origin, and hands out TLS without a certificate ritual.
Using AI coding assistants without losing control: a written plan, review every diff, keep tests green, and treat the model as a fast pair — not an oracle.
A verified, step-by-step recovery of a corrupted SQLite database using VACUUM INTO, integrity_check, and backups — including what SQLite's integrity check can and cannot catch.
A hands-on account of using an AI coding assistant to refactor a large Go codebase — hours saved, mistakes made, and whether the subscription paid for itself.
A decision framework from a developer who runs SQLite in production: when SQLite is more than enough, when PostgreSQL is worth the switch, and the honest middle ground.