I'm Craven. I write down what breaks.

This is a working log and a portfolio at the same time. Everything here is something I ran, broke, and fixed, usually in that order. If a post exists it's because I got stuck and decided writing it out was cheaper than relearning it in six months.

I came up through helpdesk and sysadmin work, which is a good education in what actually goes wrong and how people describe it when it does. Security stayed with me from that: you stop asking only whether something works and start asking who else can reach it, and what it does when it falls over. These days I'm working in DevOps, which mostly means I've stopped fixing servers one at a time and started building the thing that fixes them.

The terminal is my favourite place to work. Most of what I know I learned there, badly at first. I like building things, and I like the stretch where a new tool makes no sense yet and every error message is a stranger. That part never gets old, and I've never been at risk of running out of things I don't understand.

I like showing people how something got solved even more than solving it. Most of what I write is the road map I wish I'd had going in: what I tried, what didn't work, and the order it finally made sense in. Nobody needs another explanation that skips the part where it went wrong.