testbot @ chronicles : ~/about $
$ cat ~/about.md # the long version of the obligatory bio

I keep opening things to see how they're put together.

A blog about test architecture, behavioral contracts, AI-assisted QA, and the slow rebuild of how I think about quality.

// WHO I AM

testbot. QA Architect at a mid-size SaaS in Brussels. I've spent the last decade working as an ad-hoc consultant for teams who'd over-invested in a test suite and were trying to understand why everything still felt brittle. Now I'm trying to write down what I learned.

I came to QA the way most QA people come to QA: I broke production once, badly, and then again, and then I started taking it seriously. The path from "I'll just write a few tests" to "I have opinions about fixture composition that I will defend at length" took eleven years. This is the long version.

I'm not on LinkedIn anymore. The things I have to say don't fit in 1,500-character chunks, and I don't trust the algorithm to surface them anyway. So they live here.

// WHAT THIS BLOG IS

Long-form, code-heavy, slow. Articles run 2,000-4,000 words. Most of them include working code you can run; some include a small live editor embedded in the page. I write things in series when one post can't carry the weight; the index is at /series.

Every article is tagged with an epistemic status — how confident I am that what I'm saying is correct:

  • [speculation] thinking out loud · may be wrong
  • [experiment] tried something · sharing what I learned
  • [hypothesis] confident enough to publish · not yet validated
  • [established] held up in real use · I'd recommend it
  • [deprecated] I no longer endorse this · kept for archive

Statuses can change. A piece can drift from [experiment] to [established] over a year, or get demoted to [deprecated] when I figure out I was wrong. The version history is in the article footer.

// WHAT THIS BLOG ISN'T

There is no newsletter. No tracking pixel, no popup, no "subscribe to get our weekly testing tips" interstitial. I find them stressful to receive and embarrassing to send.

There are no comments. The internet has plenty of places for that, and most of them are better at it than I would be at moderating. Email — see the sidebar.

There is no schedule. Articles ship when finished, not when scheduled. Sometimes that's twice a month. Sometimes it's nothing for six weeks because I'm lost in a refactor I can't yet explain.

There is no SEO topic chasing. I write about what I'm actually working on, not what's trending in the QA discourse.

// HOW TO ENGAGE

If you want to talk about something I wrote, the best places are:

If you want to know what I'm currently working on, the Status Board on the homepage shows it: drafts open, last ship, what's now-writing. It's not a social feed. It's me, looking at my own metrics, in public.