Kato Coaching

@kato-coaching.com

Turning testers into trusted advisors. | Keynote speaker | Coach | Trainer Free resources and my book: https://t.mtrbio.com/kato-coaching

Everyone in QA can describe their AI's bad habits without thinking. Nobody finishes "what I really want from this tool is…" If you've been generating tests with AI and correcting the same handful of things every week, what would actually help?

The research on code review has been consistent for over a decade: it's strong at knowledge sharing, weak at catching defects. When teams insist on "humans review every line" of AI output, they're doubling down on the thing we know doesn't work. kato-coaching.com/human-in-the-loop-code-review

I have a Claude Code skill that creates google slides for me, and then adds speaker notes. Since the update to Sonnet 4.7 it constantly "forgets" how to do the latter, and tells me it's incapable of it. Anybody else have this problem? Suggestions?

The "testing mindset" isn't a personality trait. It's trained. Developers often don't think about quality the way QA engineers do because they haven't had the same deliberate practice. That's fixable, but only if the culture reinforces it too.

The Easter Bunny has 10,000 eggs to hide across 47 gardens before sunrise. His team suggests using AI to plan the hiding spots. Before handing a task to AI, run it through a simple framework. Here is how the Easter Bunny uses this framework to avoid a disaster. 🐇🥚

Can AI save the Easter Bunny?

Before you hand a task to AI, you need to know if it's actually a good candidate. The Easter Bunny has 10,000 eggs to hide across 47 gardens before sunrise. ...

youtu.be

TIL: it's much easier to get Claude Code to play nicely with the Google workspace MCP than it is to get Gemini to use it. What the hell? Yes, I am experimenting with a multiple agent setup, but man, it's painful.