ErrorZap is where I write down the technical stories that are too useful, strange, expensive, or funny to leave trapped in a terminal scrollback.
I work in managed IT, infrastructure, security, automation, backups, networks, and the untidy space where a clean diagram meets a real building full of old wiring. The posts here are field notes, not recycled product copy. Details are generalized when they could identify a client or expose a system, but the failure modes and lessons stay real.
You will also find the 90s Kid collection, because the people who survived IRQ conflicts, dial-up noise, rewinding VHS tapes, and printers that sounded like farm machinery deserve their own archive.
What you can expect
- The problem, including what made it misleading.
- The evidence that separated the real cause from the tempting guess.
- The fix, the boundary, or the lesson worth keeping.
- Enough technical detail to be useful without publishing somebody’s private infrastructure.
- A willingness to say when the machine was right and I was the problem.
ErrorZap uses privacy-first traffic and performance measurement through Cloudflare. It does not use an advertising network or build visitor profiles. See the privacy note for the short version.
For managed IT help, hire me.