Testing journey - research, projects, conferences and article library

Michal Buczko - Quality Adventures

Subscribe

AI Orchestration

Orchestrating AI delivery across model tiers — architect, orchestrator, workers — and keeping it honest.

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.

Is the token even the right unit of account?

Is the token even the right unit of account?

The honest answer is: the token might not be a unit of account at all. That's a problem, because I've spent eleven posts denominating everything in it.

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.