DAfield-noteslaeringer
Field Notes
Short notes from real sessions. One lesson per post — written short — with the raw prompts folded away underneath if you want to dig.
Field Notes are short notes from the work. Not a story, not an essay — one thing I learned, put as plainly as I can.
Each post is built in two layers. On top: the lesson itself, on a single page, no filler. Below, folded away: the raw prompts and the actual session, if you want to see exactly what was said to get there.
So you choose. Want just the point? Read the top and move on. Want the craft behind it? Unfold the rest.
Posts in this series
- 01Show the style — don't describe itThree rounds describing our brand to gpt-image-2 never hit the family. It only landed once I asked to use the two existing icons as reference. What I learned, short.
- 02I thought I'd been hackedThe box was eating itself: slow SSH, double-digit load, containers restarting at random. It looked like a cryptominer. It was just my own accumulated state — and while cleaning up, I planted a time bomb in the boot config.
- 03The box won't boot — and it's my own faultAn OOM cascade rebooted the machine. It never came back up. Four hours, a pile of dead ends and a KVM console later: GRUB was never being loaded — because five days earlier I'd erased the boot code from the wrong disk.
- 04498% committed: anatomy of a silent server death22 days of uptime, then silence at 00:40. No OOM, no panic, no logs — just a machine deadlocked on its own swap. What sysstat caught, and the one-line fix: per-container memory limits.
- 05Spawn narrow — turn off the MCP you don't needA batch job ate 30 GB of memory. The root cause wasn't the job — it was that every spawned Claude loaded an MCP server it never needed. The thing I learned, short.
