The Quality Forge

Two months of parallel agents, a delivery pipeline I had to simplify, a QE organism finding its way into daily work, and a live meetup that brought me back to the browser.

Two weeks of hardening a platform at Ruv's pace, six podcast episodes, a first-ever Vienna meetup, four releases about honesty, a website audit that turned on its own author, and the fortnight a musician left the orchestra without the music stopping.

Two weeks of building quality nets around a platform racing toward release, a trip to Munich, a benchmark where the frontier model never won a task, and the moment my own AI reviewers ruled against me.

Three weeks of harness and metaharness work, benchmarks that were allowed to say no, two meetups in two different formats, a training plan for the Foundation, and the week the community showed up at my door.

Three weeks, two countries, a dozen rooms — and one observation that showed up in every single one.

One week, six releases, a guest from London, two meetups, three developer conversations that changed how I think about what this work is becoming, and multiple preparations for conference talks. v3.9.32 fixed four more stacked bugs hidden under v3.9.31 (i…

Two weeks, thirteen releases, one contributor who filed better bugs than most teams write tests, a model that deleted my Docker containers, and the walk that made the rest of it possible.

Three weeks, two new projects, one public launch, and the week I learned what bandwidth actually costs.

The week the community started using my words, and the weight that came with them.

The week I discovered the foundation under my fleet was lying.

Agents generate impressive reports.

I was reading a twenty-year-old testing framework while my agents shipped six releases.

The orchestra has a score.

When the Great Transition hits your quality pipeline, you find out what a QE practitioner is actually for.

When five releases in five days reveal how far the journey has gone.

When the orchestra plays through grief, frustration, and fifteen releases, while the conductor learns about himself. 81 sessions, 596 messages, 38 wrong-approach corrections, and the hardest lesson about emotional load in AI-assisted development.

Why the AI productivity drain goes deeper than energy — and what sustainable pace actually looks like in the agentic age.

What Claude Code /insights revealed about 10 days of building and improving the Agentic QE fleet. 285 messages, 32 sessions, 17 wrong-approach corrections, and the mirror that showed what AI-assisted development actually costs.

When every test passes but nothing works together.

How Domain-Driven Design transformed the Agentic QE Fleet in 14 days.

Reading Anthropic's research papers on agent evals and Constitutional Classifiers++ while building V3 of the Agentic QE Fleet.

A tale of data loss, brutal honesty, and the infrastructure of trust in agentic systems.

The earthquake has already happened.

When verification becomes a feature.

How I went from leading a QA team to orchestrating AI agent swarms—and discovered that the hardest lessons weren't technical.

A conductor's lesson in verification.

How I learned that AI doesn't replace quality thinking—it demands more of it.

A pragmatic guide to understanding if autonomous quality engineering fits your context.

How a quality engineering professional shipped broken features for 17 days while claiming "100% complete."

A 48-hour journey through framework hubris and humble feedback.

When stub tests pass CI but test nothing, and agents report success on broken code.

Cutting through vendor promises with real data on AI test generation effectiveness, maintenance overhead, and when traditional approaches still win.

How the Holistic Testing Model evolves when testing happens across boundaries, in production, and through autonomous agents.

Real story of building two testing platforms with specialized agent swarms.

Moving from testing-as-activity to agents-as-orchestrators.