The chaps dig into another Keithism to see where it takes them.
Keith Klain published a blog post that drew a line in the sand for testers. His conclusion is blunt: there's a specific type of testing work that too many in our industry believe is our raison d'etre, while the market is rapidly reassessing its value (and not in a good way!).
Chapters
01:12 - Welcome (may contain traces of Premier League banter)
03:00 - Who is Keith Klain and why should you listen to him?
06:30 - Checking vs testing: what's the actual difference?
12:00 - Keith's warning: AI is coming for the…
12:56 - The CEO has one job…
14:04 - …and they have two ways to do it
15:31 - If your value isn’t the amount of tests you’ve executed, what is it?
19:42 - Richard's updated AiT principle: shared understanding over assumed understanding
23:53 - Shift left is more than "test the requirement first"
27:18 - The ways your perceived value is constantly moving.
31:57 - Maaike's stance: what if you refuse to use AI entirely?
34:09 - Too big to fail? What AI investment really means for the industry
39:53 - The skill no one taught testers that now matters most
42:54 - "Become the insufferable AI person" and other survival tactics
45:22 - Keith's call to action
47:09 - Why no one at Test Coast said "risk" when asked why they test
51:01 - AI summaries as input to other AI: the risk nobody designed for
54:00 - How one bad step ruins everything
55:27 - Statistics, Hugging Face, and the skills testers need to learn next
57:43 - There’s more than one way to “be technical”
59:54 - A rallying cry from Rich to the testing community
01:04:00 - Forward-deployed engineers: just a QE by another name?
Links to stuff we mentioned during the pod:
Episode 36
