A documentation site is not your Rails app
A WEBrick dependency in a documentation Gemfile prompted a better question: what actually runs when someone requests a page?
Topic
Pragmatic engineering, tradeoffs, product code, and decisions that survive contact with reality.
A WEBrick dependency in a documentation Gemfile prompted a better question: what actually runs when someone requests a page?
A ninety-minute padel match, two seventy-minute recordings, and the small forensic job required to turn a camera archive into the video a human actually asked for.
A practical Immich upgrade runbook built around database backups, storage measurements, exact version pins and post-upgrade invariants.
A defensive pipeline for parsing financial PDFs with layout-aware extraction, normalized data, sanitized fixtures and accounting reconciliation.
How to remove a Tailscale exit node cleanly: drain clients, withdraw routes, delete the tailnet device, clear local trust, and verify the negative space.
A small Telegram expense bot, a Google Sheet, and the operational truth that most useful automation eventually has to pass through a permissions screen.
A practical checklist for a Telegram bot that writes to Google Sheets through Apps Script, including the retry, spreadsheet, and 302 traps.
A sharper note about the moment an AI answer feels impressive for the wrong reason.
A practical note from a real homelab experiment: what mattered when running a 26B MoE model on an RTX 2070 SUPER with 8GB of VRAM.
A boring technology stack helps small teams ship, debug, and maintain software by saving attention for the product instead of the plumbing.