In continuous delivery, the pipeline is not where testing ends
Most teams treat a green pipeline as the end of testing. In continuous delivery it is the middle. The real practice is designing how cheaply you can be wrong once the change is live.
Latest
Quality at AI Speed
The model was confident and wrong. Designing for that.
Last week I argued that a quality gate earns its keep by where it sits — place the check just upstream of where the mistake turns expensive, and you catch defects while they're still cheap to fix. I stand by every word. So here's the failure that walks straight through all of it.
Gate design 101: where quality checks belong in the loop
Reviewer design: catching what the architect tier misses
Trust Is Produced, Not Felt
Quality at machine speed: ~70,000 tests, static analysis, and the review bias nobody warns you about
My conferences
Istambul Software Testing Conference 2025
My first conference in Turkey, and a critical-thinking talk in front of a room with no idea who I was. The discussion kept coming back to balancing AI with fundamentals. I now think balance is the wrong word.
TestFest : 2025
QA or the Highway 2025: the conference was one stop on a three-week research trip
The Chapter, and the Company It Keeps
Is the token even the right unit of account?
The arc ended on a stage: what a room of testers did to the thesis
CAST 2026 - Open season: what a room full of sceptics taught me about the quality gate
Leadership
Istambul Software Testing Conference 2025
My first conference in Turkey, and a critical-thinking talk in front of a room with no idea who I was. The discussion kept coming back to balancing AI with fundamentals. I now think balance is the wrong word.
Quality engineering doesn't save money. It buys the right to decide.
Your bug backlog is a list of decisions nobody made
The Chapter, and the Company It Keeps
The Speed Trap: AI Made Us Faster Than We Can Justify
BowFest 2026: what a field full of archers told me that no test suite could
From Vision to Production: the whole series, in one place
AI Orchestration
The model was confident and wrong. Designing for that.
Last week I argued that a quality gate earns its keep by where it sits — place the check just upstream of where the mistake turns expensive, and you catch defects while they're still cheap to fix. I stand by every word. So here's the failure that walks straight through all of it.
Gate design 101: where quality checks belong in the loop
The overengineering tax: when three tiers cost more than one
The Complete AI Orchestration Journey: From Claude Web Chat to Production iOS App
Reviewer design: catching what the architect tier misses
Stop prompting, start delegating
