WELCOME TO TESTINGIL
AI made your team faster. Shipping got slower.
Your developers are creating more code than any human can review. The code mostly works. But the review queue grows, there’s not enough time to test everything and then – the bugs come back.
Rework quietly eats the time you gained.
Tools help, but they have their limits too. They identify patterns, syntax errors, and exposed secrets. They can’t tell you if the code does what you actually meant, if the architecture still holds, or if the tests actually check anything meaningful.
Humans always did that part. Now there’s a lot more of it.
I work across engineering teams – developers, testers, architects, devops – to cement the judgment skills: what to verify, and how to do it effectively. So the team keeps working at the delivery speed AI promised.
The Bill Is Coming
Code You Don’t Fully Own
Your team is pushing code faster than ever. But AI-generated code that nobody fully traced, reviewed, or understands is not an asset – it’s a liability. Every sprint that passes without closing that gap adds another line to the bill.
Quality You Can’t Fully Trust
Your dashboard is green. But green doesn’t mean what it used to. When the code, the tests, and the models are all shifting underneath you, a passing suite feels like confidence. It isn’t. And false confidence is expensive.
Knowledge You Can’t Afford To Lose
When a key developer leaves, what goes with them? In an AI-assisted team, the answer is increasingly: everything that wasn’t documented, wasn’t reviewed, and wasn’t understood by anyone else. Not to mention the experience of people with the code. That’s not a people problem. That’s a process problem – and it compounds.
Who This Is For
Lead the Team
The risks are yours: your code, your architecture, your exposure. I help build the governance layer that keeps velocity high, avoiding the traps you don’t know are there.
Build and Test It
Your experience isn’t obsolete – it’s the advantage AI can’t replicate. We’ll build on what you already know and upgrade your skills to handle what the new complexity demands.
Not Sure Yet?
Start with the thinking. Webinars, articles, and tools that map the monsters before you decide what to do about them.
I’ve been writing code since I can remember. Developer, tester, manager, consultant – I’ve seen every era of software from the inside, including every wave of “this changes everything.”
AI is not the first revolution. But it is the fastest. And the one most likely to cover up the problems rather than fix them – in your codebase, in your test suites, and in the organisational knowledge your team has built over years.
The foundations don’t disappear when the tools change. Clean code still matters. Testable architecture still matters. Knowing why something works – not just that it does – still matters. That’s what gets lost when teams move fast and trust the output.
What I bring is both: the classic practices that AI skips, and the new ones built for what AI actually creates. For the developers and testers doing the work, that means a real upgrade – not just better prompts. For the leaders accountable for the outcome, it means visibility, control, and a team that owns what it ships.
Twenty-five years of knowing what breaks. And the updated toolkit for what’s breaking now.
And if I get a few minutes, I’m gonna shoot some zombies. AI or not.
The questions that the industry isn't willing to tackle yet.
Every other week: what’s actually happening with AI and software quality. Webinars, videos, articles – tomorrow’s headaches and how to prepare for them.
