Testing journey - research, projects, conferences and article library

Michal Buczko - Quality Adventures

Subscribe

Tech Leadership

Leading engineering and quality at scale — org design, decisions, and the move from practitioner to leader.

The Chapter, and the Company It Keeps

The Chapter, and the Company It Keeps

Four weeks ago I put a claim on this blog: trust in software is produced, not felt. Last week I named the four ways AI-assisted delivery quietly stops producing it, and I promised that this post would do something different — walk through what is actually inside the chapter.

Routing rules: which tier gets which task

Routing rules: which tier gets which task

Because here's the thing the token argument clears the ground for. Once you stop chasing the single best model, and stop pretending you can price the decision to three decimal places, the real skill comes into focus. It was never "which model is best." It's which task goes where.

Trust Is Produced, Not Felt

Trust Is Produced, Not Felt

Most teams treat trust as something that settles over a codebase — a feeling that builds up after enough green pipelines and enough uneventful releases. That is not trust. That is familiarity, and it feels identical right up to the morning it doesn't.

A Gate That Works, and a Gate That Only Looks Like One

A Gate That Works, and a Gate That Only Looks Like One

RPIQ, what belongs at each stage of a quality gate pipeline, and the four questions that separate a gate with teeth from expensive decoration.

Opus 5: the middle ground I actually chose

Opus 5: the middle ground I actually chose

A tool I relied on vanished, and I scrambled. I wrote a job description for the empty seat and dropped a stand-in into it. The favourite came back, and I found it a different seat rather than its old one. Then I went to a conference and let a room full of sceptics pressure-test the whole thing.

The Speed Trap: AI Made Us Faster Than We Can Justify

The Speed Trap: AI Made Us Faster Than We Can Justify

Last Saturday I promised a deeper look at what actually changes when AI enters the delivery lifecycle. This is it. The short version: the hard part is no longer producing software. It is being able to say, with evidence, why the software you just produced is safe to ship.

The arc ended on a stage: what a room of testers did to the thesis

The arc ended on a stage: what a room of testers did to the thesis

The slides and the full talk breakdown live on the other track. This isn't that post. This is the other thing that happened at CAST26, and the reason this series ended on a stage at all: seven posts' worth of argument, finally standing in front of a room that got to push back.