Written with Claude. The entire process described here — the spec generation, the triage conversation, and this blog post — was done in one Claude Code session. The Wall of Findings I have a home network infrastructure repo. Raspberry Pi running Pi-hole, Caddy, WireGuard, CrowdSec. About 20 scripts, a Go TUI dashboard, some systemd units, a security dashboard. The kind of thing that accumulates config and code over 280+ sessions of Claude Code work. ...
I had 18 services running across two Raspberry Pis and a Chrome bookmarks folder full of different ports. Every few weeks I’d need one and end up clicking through bookmarks trying to remember which port was which. How I got here I use Claude Code on a couple of Raspberry Pis. Over the past few months I kept asking it to build me things — a performance report for Podly so I could see podcast processing stats visually. A SvelteKit spec browser so I could review generated codebase specifications and give Claude specific feedback. MOSAIC prototypes so I could compare three UI directions in browser tabs and pick one. Some were full apps, some were just a python3 server pointing at an HTML file. ...
When ‘systemctl status’ says everything is fine but your network is down, you learn that hard NFS mounts and critical services don’t mix.
How an AI assistant saturated SSH connections, crashed a Pi, triggered rate limiting, and why that incident led to mandatory safety rules for AI-assisted infrastructure management.