Build log

The site went public today. This is the honest half of the story: the graveyard of finished-but-unshipped projects, fear dressed as engineering, and how making every disaster boring did what courage never could.

This week the site got its name. A plain-language tour of domains and DNS: the internet's phone book, why you rent a name rather than own it, what the dots mean, and why the name is worth more than the machine.

The night the site went public I built its backup system, and the step that matters is the one everyone skips: every night it restores its own backup into a scratch database and proves the data comes back.

The site you are reading is served from a house, and the house's door stayed shut. How outbound-only tunnels work, why default-deny suits a forgetful brain, and the kill switch that let me sleep on launch night.

A voice assistant for the house that runs entirely at home, with an honest ending where the simple option beat the clever one. Including what those AI speed numbers actually mean.

Talk to any window on your computer and have the words appear, pointed at your own server instead of a company's. The setup, why it is private, and the one likely snag.

Dictation, a chatbot and an image generator, all sharing one graphics card without crashing. The scheduling rules that made it work, instead of buying more hardware.

A graphics card turns slow dictation into instant dictation. Why it helps, how to switch it on, and the compatibility trap that sends you the wrong way.

Private speech-to-text on a computer you own, in one command. What you are building, why each step is there, and honest numbers on how fast it really is.

The most interesting part isn't the AI - it's the scaffolding that assumes the AI will be wrong and makes wrong cheap. An engineering story, not investment advice.

The full stack, the one-command deploy, the two bugs the test suite caught, and where the AI actually fits - a real build log from the server this site runs on.