Read Melissa Fisher's blog post: My rubber duck buddy — LLM use case - accelerate your thinkingShe uses Co-pilot to get her thinking in order before landing on a test strategy. Very nice indeed!&nb...

Any of my former coworkers can confirm that I can talk about QA for hours at work, where I'm comfortable; where I know the audience.  I've never done anything like the insights conversation be...

How can we manage the complexity of AI testing tools?

Are conversations the key to QA-developer relationships?

A reflective exercise in which a person examines a belief or position by asking "why does this matter to me?" three times in succession, each time responding to their previous answer. The technique is designed to move beyond surface-level rationale and surface deeper, often unstated assumptions or values. In the context of AI and testing, it was used in the MoTaverse as a way for practitioners to clarify their real reasons for embracing or resisting AI tools. It is related to the "Five Whys" root cause analysis technique, but applied to personal belief rather than system failure. For example: "I want to use AI in testing" → why? → "to save time" → why does that matter? → "so I can focus on more interesting work" → why is that important? → "because I feel undervalued doing repetitive tasks."

Clean code, messy legacy, and good products. Demi, Simon, Rolf, Nadja and the TWiQ crew get into it all.

Code that is readable and understandable by other humans, not merely executable by a machine. The underlying principle is that code is read far more often than it is written, so clarity and expressiveness are first-class concerns. A frequently cited standard comes from Martin Fowler: good programmers write code that humans can understand, not just code that a computer can run. Clean code tends to use meaningful names, small focused functions with a single responsibility, and no unnecessary duplication. — TWiQ Episode 136

Learning lots of secrets about clean code with Simon and Demi!

Bring your vacuum, feather duster and wipes because it's time for some clean code!Why bother? As Martin Fowler so gracefully puts it: "Any fool can write code that a computer can understand. Good p...

Sometimes the most effective guardrail isn't the most sophisticated one

AI needs guardrails to play by the rules and work better