In my free time, I like building prototypes, honing my craft, and solving programming katas.

Tools and Bash scripts scratch the same itch.

I run Arch Linux by choice: piecing a system together component by component teaches me far more about how an operating system actually works.

Compile-time programming fascinates me, and I'm keeping a close eye on what Reflection in C++26/29 will make possible.

Tests, to me, are a tool for confidence rather than a box to tick: they catch regressions and keep the software behaving the way it should. I mostly reach for TDD when fixing bugs: write a test that reproduces the bug, fix the bug, then confirm the test passes and nothing else broke. For new features, the tests usually come after the code, but I still design with testability in mind, pausing to think about how a class or function will be used before I write it. Coverage is useful to developers, but it says nothing to clients, sales, or managers, so the coverage level shouldn't be a target set by any of them!