The Vernon Richard Show

Vernon Richards and Richard Bradshaw

5.0 (1)
TECHNOLOGY
UPDATED BIMONTHLY

Vernon Richards and Richard Bradshaw discuss all things software testing, quality engineering and life in the world of software development. Plus our own personal journeys navigating our careers and lifes.

JAN 26

This Was Supposed to Be About Testing

This was supposed to be about testing.Instead, it turned into a conversation about burnout, money, leadership, community, AI, and what it actually takes to build a sustainable life in tech.Richard and Vernon kick off 2026 reflecting on what they’re changing, what they’re rebuilding, and how testing and quality fit into a future shaped by intention rather than hustle. Links to stuff we mentioned during the pod: 05:19 - The Malazan Book of the Fallen by Steven Erikson14:59 - The $1k Challenge by Ali Abdaal Vernon took part in last year17:23 - The video from Daniel Pink on how to have a successful yearHere's where Daniel talks about having a Challenger Network (but the whole video is 😙🤌🏾)18:46 - Toby SinclairToby's websiteToby's LinkedIn19:24 - Keith KlainKeith's blogKeith's podcastKeith's LinkedIn19:25 - Agile Testing Days conference35:45 - What is Model Drift?41:06 - Glue workTanya's Glue Work presentation which you can read or watchVernon's talk about how glue work impacts Quality Engineers, Testers, etc.48:06 - Gary "GaryVee" VaynerchukGary's websiteGary's YouTube00:00 - Intro 00:54 - Greetings & where have we been? 01:32 - The holidays 02:34 - Rest & mood 04:00 - Routines for success 05:59 - Push-up challenge! 08:35 - Dopamine detox 10:28 - THE EPISODE BEGINS! 10:29 - What are our personal 2026 themes (rather than resolutions)? 10:59 - Rich's 2026 themes 13:10 - Vern's themes 17:58 - Friendship, loneliness, and being the initiator 21:28 - Rich has a two itches. One about writing... 21:56 - ...and another about hats 25:23 - Vern's leadership focus and testing foundations 31:06 - AI work: data mindset, agents, and the vibe coding divide 40:11 - Rant about AI testing being stuck in the past 46:37 - Do "cool" shit and "talk" about it. How to stand out from AI Slop 50:10 - Our podcast themes for 2026

54 min
10/21/2025

Shifting Left: Agile vs. Waterfall in QA

In this episode of the Vernon and Richard show, the hosts engage in light-hearted banter about football before diving into a deep discussion on QA, QE, and testing. They explore the concept of 'shift left' in software development, comparing its application in agile versus waterfall methodologies. The conversation shifts to the evolving roles of QA and QE in the context of AI's impact on the industry, emphasizing the importance of task analysis and building a quality culture within teams. The episode concludes with reflections on managing expectations in QA roles and the future of jobs in the field. 00:00 - Intro 00:48 - Welcome and "Hey" (may contain traces of ⚽️) 04:45 - Olly's first question: Does shift left lend itself more to waterfall (than other methodologies)? 14:41 - Olly's second question: Does this limit how much agile can be used? Is there potentially a new methodology that can emerge from this? 22:31 - Olly's third question (remixed by Rich a little): "...is it more now a case of making people aware that they can, should be considering things ahead of development?" 34:24 - Olly's fourth question: How far can you shift-left before it becomes overstepping? 51:53 - Olly's... which question is this now?! Next question! That works!: Where does the QA role end? Links to stuff we mentioned during the pod: 04:26 - Olly FairhallOlly's LinkedInHere's a link to what Olly sent us04:45 - Waterfall (in software development)Wikipedia article about the history of the term This article goes into a little more detail about the different phases and characteristics of the model 07:29 - Dan Ashby's (yes DAN'S!) famous diagram is part of his often cited "Continuous Testing" post07:50 - For folks who don't understand that reference, it's... taken (🥁) scene from the movie Taken08:10 - Rich's Whiteboard used to get a lot more love😞 22:31 - Olly's questions and thoughts that are guiding our conversation. Thanks Olly!44:12 - The book "Who Not How" by Dan Sullivan and Dr. Benjamin Hardy46:33 - Elisabeth HendricksonGet Elisabeth's excellent book Explore It!Elisabeth's LinkedIn46:49 - Alan PageAlan's newsletterAlan and Brent's podcastAlan's LinkedIn51:53 - Kelsey HightowerKelsey did a Q&A at Cloud Native PDX and you can listen to the question and answer I was trying to describe here.I urge you to listen to the whole thing. Kelsey is an excellent orator, storyteller, and all-around human ❤️55:33 - Rob SabourinMy quick Perplexity search for Rob's public material on Task AnalysisRob's Linkedin56:59 - Vernon's newsletter "Yeah But Does it Work?!"The issue mentioned is called "What Is The Vaughn Tan Rule and How Does It Impact Testing?" and talks about where we might start with unbundling

1 hr
10/01/2025

Measuring Software Testing When The Labels Don’t Fit

This episode is about the struggle to explain, measure, and name the work testers and quality advocates actually do — especially when traditional labels and metrics fall short. Links to stuff we mentioned during the pod: 05:05 - Defect Detection Rate (DDR)The rate at which bugs are detected per test case (automated or manual)No. of defects found by test team / No. of Test Cases executed) *10015:06 - David Evans' LinkedIn24:57 - Janet GregoryJanet's websiteJanet's LinkedIn26:01 - Defect Prevention RatePerplexity search results here28:28 - Jerry WeinbergJerry's Wikipedia page (his books are highly recommended)49:33 - Shift-Left: The concept of moving testing activities earlier in the software development lifecycyle. Some resources explaining the Shift-Left concept (Perplexity link) 00:00 - Intro01:11 - Welcome & "woke" testing 😳03:15 - QA, QE, Testing… whatever we call it, how do we measure if we're doing a good job?03:44 - Vernon’s first experience with testing metrics: more = better?05:00 - Defect Detection Rate enters the chat06:41 - Rich reverse engineers quality skills needed in the AI era10:54 - How do we know if we’re doing any of this well?12:40 - Trigger warning: the topic of coverage is incoming 😅16:54 - Bugs in production21:09 - Automation metrics: flakiness, pass rates, and execution time24:29 - Can you measure something that didn’t happen? (Prevention metrics)27:43 - Do DORA metrics actually measure prevention?32:03 - Here comes Jerry!33:50 - The one metric the business cares about...36:23 - QA vs QE: whose “quality” are we "assuring"?39:25 - What's the story behind the numbers?48:29 - Rich brings in Shift Left Testing50:14 - Metrics that reach beyond engineering53:14 - Rich gets a new perspective on QE and the business56:50 - Who does this work? Testers? QEs? Or someone else?

1 hr
09/09/2025

When Everything Sounds Like Testing… How Do You Explain What You Really Do?

In this episode, Richard and Vernon delve into the complexities of Quality Assurance (QA), Quality Engineering (QE), and testing in software development. They explore the evolution of these concepts, their interrelations, and the importance of metrics in assessing quality. The conversation highlights the need for a holistic approach to quality, emphasizing that both prevention and detection of bugs are essential. The hosts also discuss the challenges of defining these terms and the future of quality in the industry. Links to stuff we mentioned during the pod: 08:50 - Dan AshbyWe're referring to Dan's's excellent post called "Continuous Testing" (featuring his famous diagram!)17:13 - Jit GosaiJit's blog Jit's Quality Engineering Newsletter Jit's LinkedIn19:24 - Quality Talks PodcastStu's Quality Talks podcast that he co-hosts with Chris HendersonStu's LinkedInChris's Linkedin19:55 - The Testing Peers podcast22:00 - DORA Metrics: DORA metrics are a set of key performance indicators developed by Google’s DevOps Research and Assessment team to measure the effectiveness of software delivery and DevOps processes, focusing on both throughput and stability26:13 - A link from Episode 10 where Vern discusses Glue Work (be sure to check out the show notes on that episode)Quick overview of DORA metrics34:43 - The Credibility PlaybookA video course by Vernon as he experiments with building digital products.Check it out and let him know what you think of it! 😊46:24 - Ali AbdaalAli's websiteAli's YouTube00:00 - Intro 01:36 - Welcome 02:40 - Today's topic: What the hell is QA? QE? Testing? And is it all changing? 03:00 - Why is this bugging Rich? 05:11 - Fruit fly tangent 🍌🍊🍎🪰🐝🦋 06:27 - Rich's take on QA, QE, and Testing 08:31 - Vern's take on QA, QE, and Testing 11:15 - Is shift-left testing the same as QE? 13:05 - When the team tests early... is that QE then?! 16:18 - What's the big deal if we can’t define QE clearly? 19:27 - Why the Efficiency Era makes this even harder 22:55 - Trying to draw the Testing, QA, QE, Venn diagram 27:24 - Getting the QA, QE, Testing blend just right. What's the right mix? 29:52 - The kinds of work we take on as our careers grow 34:08 - What Testers get rewarded for 45:34 - How Ali Abdaal helped Vern think differently about quality 48:18 - Rich talks measurement

54 min
08/26/2025

Embedding Quality Using AI

In this conversation, Vernon and Richard explore the evolving role of AI in quality engineering and software development. They discuss how AI can enhance quality control processes, the importance of embedding quality early in the development cycle, and the potential challenges and opportunities that arise from integrating AI tools. The conversation also touches on the need for skill development and community engagement in adapting to these changes, as well as the implications for roles within the industry. Description and Thumbnail made with AI to assess the quality, we had to! 00:00 - Intro01:02 - Welcome and footy ⚽️02:15 - Today's topic: The impact that AI may or may not have on Quality Engineering03:22 - Rich's wild idea about AI and software quality14:10 - Vern asks a clarifying question22:45 - Communities of excellence… for machines?!24:03 - Vern thinks there's an obvious risk that follows from this idea...31:31 - Rich addresses the risk (Oracles, prompts, and tester superpowers)36:13 – Reflection: the hidden skill AI forces on us41:40 – Shifting in all directions (not just left)43:04 - Feeding your past self into an AI: smart or scary?45:53 – Operation 400 subscribers (and bot listeners)47:13 – Tony Bruce calls us out on sloppy show notes and outro Links to stuff we mentioned during the pod: 04:18 - Shift-Left: The concept of moving testing activities earlier in the software development lifecycyle.Some resources explaining the Shift-Left concept (Perplexity link)25:35 - Rob BowleyRob's LinkedInThe post Vernon referred to......a follow-up post not long after that one too!26:40 - Alan PageAlan and Brent's podcastAlan's LinkedIn34:43 - Saskia CoplansDigital Interruption Saskia's cybersecurity consultancyREXscan Saskia's automated mobile application vulnerability scannerSaskia's LinkedIn (highly recommended follow)41:49 - Paul ColesPaul Coles published 3 of his 4 part series "The Subtle Art of Hearding Cats" over on Dev.To Recommended reading!Paul's LinkedIn43:09 - Maaret PyhäjärviMaaret's websiteMaaret's blogMaaret's LinkedIn

48 min
08/04/2025

Six Hard Lessons From Building With AI Agents

In this episode of the Vernon Richard show, the hosts discuss their experiences with AI tools and agents, focusing on the challenges and lessons learned from using these technologies in coding and software engineering. They explore best practices for utilizing AI effectively, the importance of context in interactions with AI, and the future of AI agents in the workplace. The conversation highlights the balance between leveraging AI for efficiency while maintaining control and understanding of the underlying processes. Links to stuff we mentioned during the pod: 09:16 - The LinkedIn post talking about Replit messing with someone's production code 😳And the link to the thread of person who went through itThe tool in question, Replit13:01 - Rich's LinkedIn post with his tips14:21 - GitHub Copilot18:09 - VS Code29:01 - Folks at different ends of the "AI Enthusiasm Spectrum"On the enthusiastic endJason Arbon is on the positive side and is always creating something interesting like...testers.aiOn the unenthusiastic endKeith Klain has created a reading list to help get us up to speed...Keith's reading AI reading listYou can see his full resources list hereMaaike Brinkhof has a bunch of thought-provoking posts on the topic......like this oneand this one34:44 - Want to know what "conflabulation" means? Listen to Martin explain it on the Ghost in th code podcast (that's not a typo!)37:24 - What is Context Engineering? Perplexity has answers!46:38 - The legendary Lt. Geordi La Forge from Star Trek: The Next Generation.51:48 - After recording, the very cool Paul Coles published his article The Subtle Art of Herding Cats: Why AI Agents Ignore Your Rules (Part 1 of 4, explaining the topic of Context Engineering. It’s brilliant!59:04 - The promises of technology over the years...60:50 - The always insightful Meredith Whittaker of Signal fame, where is the president and services on its board of directors, explains the privacy and security concerns with agentic technology. Watch the clip, then go back and watch the whole thing! 00:00 - Intro01:17 - Welcome01:30 - TANGENT BEGINS... All kinds of egregious waffling follows. Skip to the actual content at 08:3401:31 - Rich VS Tree Stump01:57 - What on earth did Rich need the pulley for?02:26 - Vern's nerdy confession and pulley confusion02:52 - Does Rich live next door to Tony Stark?!03:22 - What to do when you need a steel RSJ03:35 - We admit defeat. 03:36 - Welcome to Rich's Garden Adventures Podcast!07:25 - What has Vern been up to?08:34 - We attempt to segue into the episode at last!08:35 - TANGENT ENDS...08:51 - Rich’s POC: using agents to help build AI tools09:45 - The Replit disaster: vibe coding meets deleted production data 11:12 - Sociopathic assistants and the case for AI gaslighting 11:55 - Vernon wants his team experimenting with AI tools12:50 - Rich explains the context for his latest AI adventures13:18 - Rich’s bench project and “putting the engineering hat on” 15:22 - Setting up the stack and staying in control 16:53 - A familiar story: things were going fine until they weren’t 17:00 - Ask vs Edit vs Agent mode in Copilot explained 19:06 - The innocent linting error that spiralled out of control 21:16 - Stuck in a loop: “I didn’t know what it was doing, but I let it keep going” 22:11 - The fateful click: “I’m going to reset the DB” 23:10 - The aftermath: no data, no damage… but very nearly 23:33 - Security wake-up call: agents are acting as you 24:39 - You can’t fix what you don’t know it broke 25:52 - Can you interrupt an agent mid-task? 27:14 - When agents get “are you sure?” moments 28:15 - Tea breaks as a dev strategy: outsourcing work to agents 29:24 - Jason Aborn vs Keith & Maaike: where Rich sits on the AI enthusiasm spectrum 30:41 - Tip1. The first of Rich’s 6 agent tips: commit after every interaction32:12 - Why trusting the “keep all” button is risky 34:01 - Writing your own commits vs letting the agent do it 35:26 - When agents lose the plot: reset instead of fixing 36:55 - “You’re insane now, GPT. I’m giving you a break.” 37:54 - Tip 2: Make the task as small as possible 39:59 - The middle ground between 'ask' and full agent delegation 41:12 - Tip 3: Ask the agent to break the task down for you 43:36 - The order matters: why you shouldn’t start with the form UI 44:33 - Vernon compares it to shell command pipelines 45:09 - It can now open browsers and run Playwright tests (!) 46:23 - Star Trek and the rise of the engineer-agent hybrid 47:57 - Tips 4–6: Test often, review the code, use other models 49:39 - Pattern drift and the importance of prompt templates 50:51 - Vernon’s nemesis: m dashes, emojis, and being ignored by GPT 51:48 - Context engineering vs prompt engineering 52:43 - When codebases get too big for agents to cope 53:40 - Why agents sometimes act dumber than your IDE 54:32 - The danger of outsourcing good practices to AI 54:48 - Spoilers: Rich’s upcoming keynote at TestIt 55:01 - Agents don’t ask why — they just keep going 56:42 - Goals vs loops: when failure isn’t part of the plan 58:32 - The question of efficiency: is training agents worth it? 59:47 - Rich’s take: we’ll buy agents like we buy SaaS 61:08...

1h 8m
07/21/2025

Coaching Developers on QE

In this episode of the Vernon Richard Show, Richard and Vernon discuss the challenges and opportunities in coaching software engineers on quality engineering. They explore personal updates, family dynamics, and the importance of perspective in quality and risk management. The conversation delves into the significance of code quality, effective communication, and the role of engineers in ensuring quality. They also touch on the need for hands-on learning and practical application in quality engineering training, concluding with a call to action for listeners to share their experiences and insights. Links to stuff we mentioned during the pod: 01:16 - Llandegfan Exploratory Workshop in Testing aka LLEWTYou can read about the latest edition from James (I haven’t written anything up yet - VR)19:57 - The “I just want to write code” LinkedIn postFAILURE! I couldn’t find the LinkedIn post I was referring to 😭22:29 - Linda Van De Vooren (massive brain freeze - I couldn't remember Linda's last name properly! Sorry Linda 🤦🏾‍♂️)25:04 - Cul-de-sacThis is a French term (that means "bottom of the bag") that we use in English to describe a dead-end street, i.e. a street that only has one entry/exit point.We also use it in the context Vernon just did, to indicate a situation where we have no options.31:45 - The Deep Dive tracks at Agile Testing Days look incredible! Get your tickets ASAP folks!They also have an Online Pass available if you're unable to visit Berlin (although if you can, we recommend visiting in person!)34:20 - Rich's Qt testing articlesWhere Does AI Fit in the Future of Software Testing?Applying the SACRED Model to Build Reliable Automated TestsThe Importance of Technical System Knowledge4 Essential Types of Automated API TestingExploring the Different Types of Automated UI TestingThe Manual Testing and Automated Testing Paradox42:11 - PeersCon tickets are available now. If you're in the UK and can easily get to Nottingham, I highly recommend visiting!Don't forget they also need VolunPeers (do you see what they did there?), before and during the event, so check that out too please 🙏🏾43:55 - Heather Reid Heather's blog Heather's LinkedIn46:15 - Liza, the awesome teammate in question46:41 - European Testing Conference led by Maaret PyhäjärviWhile the event has stopped, you can still take a peek at their website00:00 - Intro00:48 - Welcome ramble05:25 - Rich's question: An Engineer colleague wants to be coached on Quality Engineering, what do I do?08:24 - Vern goes into coaching mode (shock!)09:35 - Vern goes into teaching mode (shock!)10:04 - Where could we start?12:25 - Risk enters the chat...14:50 - Quality enters the chat...15:48 - Help them speak up and become a QA (Question Asker)17:30 - Two powerful questions to get them thinking about quality19:15 - The dangers of acting like an order taker...19:57 - ...or are they?21:45 - Uno Reverse! Is it true that all Engineers "love" writing code?23:18 - Order Takers vs Experts24:30 - Another powerful question to ask25:47 - Rich's clarification sparks an idea about hats27:17 - Slalom Sponsorship Appeal27:41 - How do you decide when you have learned enough on a given topic?29:21 - Majors and minors30:55 - Learning modalities31:42 - Learning tools35:00 - A "syllabus" or roadmap starts to emerge36:50 - What can the Engineer do to help the QEs in their life?43:29 - Send us your ideas please45:54 - The 1-to-many approach47:53 - The classic mistake to avoid in this situation49:15 - The relationship between testing and quality52:10 - Vernon's people will contact Slalom's people

54 min
07/01/2025

Growth Plans for Technical Testers: Why Playwright Isn’t Enough

In this episode of the Vernon Richard Show, Richard and Vernon discuss the growth plans for testers in test automation, focusing on the importance of coding skills, exploratory testing, and the balance between generalist and specialist roles. They explore the need for measurable targets in personal development plans and the significance of understanding the context of problems in software development. The conversation also touches on the impact of AI on software engineering and the necessity for collaboration between testers and developers. 00:00 - Intro 01:42 - The Ramble begins 07:39 - QUESTION (Thanks Thierry!): "How do you see a growth plan for testers in test automation as a personal development plan?" 10:12 - How has Vern helped Testers create an automation development plan? 13:14 - What does it mean to go from novice to advanced? 15:15 - Rich wants to know what test automation means before answering the question! 15:57 - The nuance (and trap!) of the word "tool" 17:35 - Rich has come up with a new term for old testing 19:21 - What about code? Which languages should you learn? 20:34 - Vern's answer to a Redditor asking a similar question 23:34 - Don't forget the reason why we're trying to learn all of these tools and languages 24:24 - Who makes the "best" "automation" testers? 25:45 - What does it look like when an SDET hasn't learned how to identify the right test? 26:34 - Ok if that's you and your team, how can you make it work? 28:33 - Lord of the Rings testing! 29:40 - How does Alan Richardson defeat "Testing Sauron"? (I'll stop the LotR references now I swears it 😇) 31:07 - Noah Sussman's excellent early ideas to solve this problem 32:42 - Generalist or Specialist, what is the core, foundational knowledge needed to call yourself an engineer? 34:18 - ...and what about AI? (only took half an hour!) 35:10 - Vern wants to get back to work asap and start creating growth plans... but for who? 38:20 - What two things are often missed in growth plans? 40:41 - Rich talks about the tangible difference between being a novice and advanced SDET/Automation Specialist/Toolsmith 41:39 - The cognitive load of your engineers 42:17 - Production code vs Automation code: Which is more important? Rich breaks it down. 44:27 - What are we optimising for? 47:45 - Do we have to choose between readability and efficiency though? 52:52 - Learning through pain 54:12 - Rich and Vern wonder what they should do next 54:32 - What makes this relevant in today's job market 55:22 - One last wild take about software development careers... Links to stuff we mentioned during the pod: 03:23 - The Øredev conference in MalmöGet your tickets here!04:13 - The LLEWT peer testing workshopCheck out this summary from last years event by James ThomasRead about the origins of this flavour of workshop06:40 - Cynefin a sense-making framework devised by Dr Dave SnowdenHere's Dr Snowden explaining the frameworkEnabling ConstraintsThe Paradox of Choice (which I didn't know was a book - readingList++)07:39 - Here's the full question from Thierry as he asked it on LinkedIn14:14 - "GUI Automation"A term used to describe tools focused on driving browsers. Some examples of such tools would include Selenium, Cypress, Playwright, and Watir.15:57 - I'll link to Rich's article once it's published 🙂16:04 - Automation in Testing (AiT)Automation in Testing references (via Perplexity)16:18 - Some tools and frameworks Rich mentioned:SeleniumPlaywrightJUnit18:50 - Rich's API Testing article on Qt QA blog19:07 - Rich's article explaining the different kinds of GUI Automation19:21 - What's a scripting language vs an object-oriented language?According to PerplexityKey takeaway: These are not mutually exclusive terms and label to two different aspects of programming languagesScripting: how code is runObject-orietned: how code is organised19:36 - Programming languagesTypeScriptJavaC# (pronounced "See-Sharp")JavaScript19:52 - Mark WinteringhamMark's websiteMark's GenAI bookMark's LinkedIn20:34 - The article called "Career Advice For A 35+ Year Old Manual Tester"26:54 - Erik "I love orange" DavisErik's LinkedIn27:42 - Rich's S.A.C.R.E.D. model29:40 - Alan RichardsonAlan's websiteAlan's Patreon communityAlan's LinkedIn31:02 - Noah SussmanNoah's stupendous blog post "How to teach yourself to be a technical tester: some thoughts."Noah's LinkedInHighly recommend that you watch Noah's talks on anyOfTheThings32:24 - Then the effervescent Michael Larsen actually went through the thing!He documented his journey with it too.

57 min

See All (32)

Creator

Vernon Richards and Richard Bradshaw
Years Active

2024 - 2026
Episodes

32
Rating

Explicit

The Vernon Richard Show

Episodes

This Was Supposed to Be About Testing

Shifting Left: Agile vs. Waterfall in QA

Measuring Software Testing When The Labels Don’t Fit

When Everything Sounds Like Testing… How Do You Explain What You Really Do?

Embedding Quality Using AI

Six Hard Lessons From Building With AI Agents

Coaching Developers on QE

Growth Plans for Technical Testers: Why Playwright Isn’t Enough

About

Information