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:
00:00 - Intro
01:17 - Welcome
01:30 - TANGENT BEGINS... All kinds of egregious waffling follows. Skip to the actual content at 08:34
01:31 - Rich VS Tree Stump
01:57 - What on earth did Rich need the pulley for?
02:26 - Vern's nerdy confession and pulley confusion
02:52 - Does Rich live next door to Tony Stark?!
03:22 - What to do when you need a steel RSJ
03: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 tools
09: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 tools
12:50 - Rich explains the context for his latest AI adventures
13: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 interaction
32: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...
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:
00:00 - Intro
00:48 - Welcome ramble
05: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 quality
19: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 Experts
24:30 - Another powerful question to ask
25:47 - Rich's clarification sparks an idea about hats
27:17 - Slalom Sponsorship Appeal
27:41 - How do you decide when you have learned enough on a given topic?
29:21 - Majors and minors
30:55 - Learning modalities
31:42 - Learning tools
35:00 - A "syllabus" or roadmap starts to emerge
36:50 - What can the Engineer do to help the QEs in their life?
43:29 - Send us your ideas please
45:54 - The 1-to-many approach
47:53 - The classic mistake to avoid in this situation
49:15 - The relationship between testing and quality
52:10 - Vernon's people will contact Slalom's people
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:
In this episode of the Vernon Richard Show, the hosts discuss the significance of social media and community interaction in the software testing field. They explore how social media has evolved, the importance of content creation, and the balance between personal goals and professional networking. The conversation also touches on their favorite podcasts and books, as well as future directions for their own show.
00:00 - Intro
00:46 - Welcome (Tiredness, Sleeper walls, sweaty chilli, and strongman training)
05:59 - QUESTION (Observation? Comment? Ramble? Whatever it is, thanks Olly!): How important is social media and community interaction to testing?
06:46 - Vernon's experience of social media over the years
08:30 - The impact of the "Influencer" phenomenon on testing
09: 59 - The golden age of Testing Twitter
10:57 - What LinkedIn can't replace
12:10 - The LinkedIn algorithm is weird!
13:15 - Algorithm anxiety and the overthinking spiral
15:45 - Community: planned vs organic
17:24 - Lurkers, reactors, and why it still counts
18:04 - To be or not to be... an influencer?
20:07 - Rich reflects on the impact of social media on him and testing
24:00 - Vern reflects on the impact of social media on him and testing
25:35 - The power of sharing with purpose (not just promoting yourself)
27:19 - QUESTION (From Olly): There seems to be a push to create content. What do you think about that?
30:12 - What is "content" anyway?
31:09 - Angie's 1-2-punch for content creation (that we should all copy!)
32:39 - Do you know why you're posting in the first place?!
33:23 - The impact of talking about testing (it's not just about "likes")
37:35 - Rabbiting on about writing
40:31 - Talking vs Doing
41:12 - Goal confusion & content fatigue
44:20 - Now that we mention it, what are OUR goals for content and social media?!
48:47 - QUESTION: What podcasts do you listen to, what books do you read, and do any of them influence what you'd like to do with the show?
57:20 - Where are we taking the podcast?
58:24 - Is Salesforce as dull as Rich thinks?
59:35 - Outro
In this episode of the Vernon Richard Show, Vernon and Richard discuss various topics, including personal updates, mental health, the role of gatekeeping in quality assurance, mentoring experiences, and effective onboarding strategies. They emphasise the importance of community support, advocating for mental health awareness, and the nuances of being a gatekeeper in professional settings. The conversation also delves into the dynamics of mentoring, the significance of setting clear goals, and the art of making suggestions in new environments.
00:00 - Intro
01:06 - Where have we been for a month?
06:16 - Men's Mental Health
09:46 - The Questions!
10:10 - QUESTION: To gate-keep, or not to gate-keep? That is the question from Deb Sherwood
22:05 - Olly impersonates Emily
22:33 - QUESTION: Mentorship advice
27:25 - Coaching vs Mentoring
28:10 - Vern's good and bad with experiences mentoring
28:57 - What role does accountability play in this?
29:38 - Informal mentoring
30:48 - Rich shares his experience mentoring a colleague
31:46 - Rich's good and bad experiences with mentoring
33:44 - Putting 💰 on the line
35:45 - Energy Vampires 🧛🏾
37:16 - The upside of being a mentor
39:17 - QUESTION: Onboarding into a new team or to a new product
40:40 - Rich's two-step process when he's in this situation
43:50 - Vern's kids teach him a valuable communication technique
45:24 - "Asking" & "Suggesting"
48:28 - The danger of suggesting things blindly
51:15 - Leadership inception
54:40 - Outro
Links to stuff we mentioned during the pod:
Summary
In this engaging conversation, Vernon and Richard celebrate Liverpool's recent football victory while seamlessly transitioning into a discussion about automation in testing. They explore the definitions of automation, the importance of having a unified codebase for tests, and the challenges of choosing the right programming language for testing tools. The duo emphasizes the significance of collaboration between developers and testers, the need for regular review of tests, and the impact of context on decision-making in automation. The conversation is filled with insights and practical advice for anyone involved in software testing. In this conversation, Vernon and Richard explore the complexities of development and testing, focusing on the importance of language consistency, the role of developers in testing culture, and the challenges of tool standardization. They discuss the perception of automation skills in the industry, the distinction between coding and technical skills, and the need for context in automation. The conversation also touches on the future of AI in development and the balance between technical skills and automation. Finally, they share upcoming events and opportunities for community engagement.
* AI Generated show notes
00:00 Football Triumphs and Rivalries
01:43 Diving into Automation
04:28 Understanding Automation in Testing
05:58 Frameworks and Code Repositories
08:29 The Role of Developers in Automation
11:08 Challenges in Automation Implementation
13:11 Best Practices for Test Code Management
19:13 Building Communication Between Components
21:13 Understanding Context and Testability
23:21 The Dilemma of Skipping Tests
25:29 The Importance of Test Review and Discipline
27:55 Navigating Commercial Pressures in Testing
29:32 The Complexity of Automation in Different Languages
42:16 The Misconception of Technical Skills in Automation
45:45 The Automation Misconception
48:44 Technical Skills vs. Coding Skills
52:32 Understanding the Role of Automation
56:01 The Future of Testing in an AI World
59:46 The Value of Critical Thinking in Testing
01:03:36 Navigating the Job Market as a Tester
01:08:48 Upcoming Events and Community Engagement
In this episode, Richard and Vernon discuss various aspects of job stability in the tech industry post-pandemic, the impact of innovation on job longevity, and the dynamics of accidental management. They explore the changing landscape of tech roles, the importance of ratios between developers and testers in projects, and the evolving nature of go/no-go decisions in software releases. The conversation emphasizes the need for clear metrics and standards to facilitate smoother decision-making processes in tech teams.
00:00 - Intro
01:07 - Welcome to the Vernon Richard Emily Show
01:35 - Our viral moment
03:07 - Question: Do you think people are staying in tech jobs longer since the pandemic? The old time in role used to be about 2 years right?
17:00 - Income worries and diversification
20:20 - Question: I see loads of developers become accidental managers, but i don't think that's as common for testers - what do you think?
23:40 - Can Testing specialists become Engineering Managers (and beyond)?
26:06 - How does being a Quality Engineer impact your chances?
28:25 - Lived experience vs coaching
31:08 - We're already doing management and leadership
32:19 - What career paths are open to people with a testing background?
33:59 - Question: Do you think there is a good target ratio of dev:test professionals in greenfield projects? Brownfield projects etc. If not, what sort of thing do you think that depends on?
34:40 - It depends! On the project demands
35:20 - It depends! On what kind of people are in the team
37:10 - It depends! On testability
37:33 - And Rich's answer is...
39:19 - Sometimes you can't coach your way out of a situation
40:50 - It depends! On what good looks like
41:25 - It depends! On where the company is in it's life
44:35 - Question: My team release software to customers 1-2 times a week. Who do you think should be in that "go/no go" conversation?
46:46 - It depends 🤦🏾♂️
48:16 - go/no go meetings in 2002 versus 2025
Links to stuff we mentioned during the pod:
In this episode of the Vernon Richard Show, Richard and Vernon delve into the intricacies of career journeys in software testing, discussing the significance of job titles, the importance of positioning oneself within a role, and the challenges faced in consulting. They explore how to define one's role and impact, navigate client expectations, and the evolution of job descriptions in the tech industry. The conversation emphasizes the need for continuous learning and adapting to different contexts, ultimately highlighting the importance of effective communication and self-reflection in shaping a successful career.
00:00 Introduction to the Podcast and Career Journeys
03:49 The Importance of Job Titles
10:08 Positioning and Expectations in Roles
20:37 Defining Roles and Responsibilities
27:47 Evolution of Testing Roles
29:09 Navigating Challenges in Testing
30:08 The Role of Leadership in Quality Assurance
31:09 Understanding Job Expectations in Consulting
32:28 The Importance of Experience in Consulting
34:38 Context Gathering for Effective Consulting
36:33 Identifying Root Causes in Testing Issues
37:25 Adapting Responses Based on Context
38:51 The Art of Job Crafting
41:38 Shifting Perspectives on Best Practices
44:16 Balancing Expectations and Reality in Consulting
47:17 Recognizing When to Walk Away
48:39 The Impact of Context on Job Titles
51:48 Reflecting on Skills Beyond Job Titles
Summary
In this episode, Vernon and Richard reflect on their experiences at the PeersCon conference, discussing the engaging keynote speakers, insightful workshops, and the overall atmosphere of the event. They share their thoughts on various talks, emphasizing the importance of communication, quality, and personal growth in the software testing industry. The conversation highlights the value of community and collaboration, as well as the significance of learning from both successes and failures in one's career. In this episode, Vernon and Richard reflect on their experiences at PeersCon, discussing memorable moments, workshops attended, and the importance of communication in the testing field. They delve into specific workshops like Pipeline and Risk Storming, and the game 'Defend the Indefensible', which encourages critical thinking and perspective-taking. The conversation also touches on feedback for future events, emphasizing the need for a balance between communication and testing topics, and the importance of recognizing the efforts of event organizers.
Chapters
00:00 Introduction and Conference Overview
03:42 Reflections on PeersCon and Community Engagement
06:35 Keynote Highlights and Speaker Insights
09:30 Workshops and Learning Experiences
12:29 Communication and Quality in Software Development
15:27 Personal Growth and Career Development
18:22 Closing Thoughts and Future Events
25:06 Exploring Engaging Talks at the Conference
27:57 Tom's Journey: From Manufacturing to Software Testing
29:10 Linda's Comedy of Errors: A Unique Perspective on Automation
32:43 The Reality of Coding: Enjoyment vs. Competence
39:37 Networking and Unexpected Encounters at the Venue
42:57 Workshops: Enhancing Technical Understanding and Communication Skills
52:17 The Importance of Communication in IT and Life
54:39 Feedback and Constructive Criticism
57:36 Balancing Communication and Testing in Conferences
01:00:29 Enhancing Event Experience and Sponsor Engagement
01:04:34 Acknowledging Organizers and Their Contributions
01:08:34 Sustaining Affordability and Accessibility in Events
Links to come!
In this episode of the Vernon Richard Show, the hosts delve into the nuances of Continuous Delivery and Continuous Deployment, exploring how testing practices evolve in these environments. They discuss the skills required for testers, the importance of risk management, and the cultural shifts necessary for effective quality assurance. The conversation highlights the need for collaboration within teams and the role of testers as facilitators rather than gatekeepers. The episode concludes with reflections on the importance of understanding quality and risk in software development.
Links to stuff we mentioned during the pod:
Bonus links to further study on the topic:
00:00 - Intro
01:06 - Merch tangent
02:53 - Today's topic:
04:08 - ⚽️ Footy
04:40 - Compare and contrast
07:00 - What conversation(s) needs to happen before "pressing the button" and who needs to be involved in it?
08:25 - Deployed Vs Released
13:37 - Monitoring and tooling to enable CI/CD practices
17:25 - Where/how do reviews fit into this?
20:38 - Back to Shift Left!
23:51 - Where does the testing happen?
24:36 - The link between chef Gordon Ramsey and software testing
25:45 - What are we reeeally talking about here?
27:09 - How to reframe things when someone makes the polarising claim "We don't need Testers in CI/CD/DevOps teams"
29:35 - Q: So how would I test differently if I were a Tester in a CI/CD team? A: Test like Jason Bourne.
32:00 - The value of having a tool belt and using it regularly
33:06 - How to catch a unicorn? How to unbundle testing skills
35:40 - This all loops back to risks & culture
37:03 - Where would it be a bad idea to use Continuous Deployment?
40:45 - Q: So how would I test differently if I were a Tester in a CI/CD team? A: Test like a Circus Ringmaster.
42:39 - Moar Shift Left: Real Devs build on Main
48:48 - Modern Vs Traditional mindsets
50:30 - Quality enters the chat...
51:00 - The relationship between risk and quality
52:47 - Testing Vs Quality Engineering
55:50 - ⚽️ Footy
In this episode, Vernon and Richard celebrate their love for the software testing community, discussing the importance of people, tools, teaching, and the thrill of conferences. They reflect on personal growth, the challenges of production issues, and the joy of mentoring others. The conversation emphasizes the connections made within the industry and the shared experiences that enrich their careers.
Links to stuff we mentioned during the pod:
00:00 - Intro
01:11 - Is it our birthday yet?
01:52 - The Forced Socio-Economic Day episode
02:20 - What do we love about our careers?
03:07 - We love PEOPLE
04:39 - Different kids of friendship
06:08 - Making a huge impact on people with tiny interactions
08:18 - The benefit of being tool aware
10:10 - We love TOOLS
10:20 - Rich's favourite tool
12:03 - Vern's favourite tool
15:40 - We love the VARIETY
18:21 - We love TEACHING
19:58 - What does the balance look like between teaching, mentoring, and coaching in Rich's current role
22:33 - We love CHALLENGE
23:51 - Systems thinking and understanding how things work
27:28 - We love CONFERENCES
35:35 - Mutual appreciation ❤️
36:28 - The Friendly Tester is Dead. Long Live Richard Bradshaw!
In this conversation, Richard and Vernon delve into the evolving landscape of AI, particularly focusing on the concept of agentic AI. They discuss personal updates, including their health and fitness journeys, before transitioning into a detailed exploration of AI technologies. Richard shares his recent experiences with AI training and projects, emphasizing the differences between traditional generative AI and agentic AI.
The discussion highlights the importance of goals, tasks, and tool awareness in AI, drawing parallels to software testing and the dynamics of generalists versus specialists in the tech industry. The conversation concludes with reflections on the implications of these technologies for the future. In this conversation, Vernon and Richard explore the evolving landscape of AI, particularly focusing on agentic AI and its implications for testing and quality assurance.
They discuss the importance of defining clear goals and expected outcomes for AI tasks, the need for quality characteristics in AI outputs, and the critical role of human oversight in AI decision-making. The conversation also touches on iterative learning, exploratory testing, and the future of AI in the testing domain, emphasizing the necessity for testers to adapt and enhance their skills in this rapidly changing environment.
Links to stuff we mentioned during the pod:
00:00 - Intro
01:14 - Welcome
04:02 - Rich's adventures learning about AI
05:24 - Rich goes down the Agentic AI rabbit hole
07:00 - GenAI vs Agentic AI
12:45 - Understanding Agentic AI vs. Traditional AI
13:27 - What's the difference between the term "Agent" and "Agentic"?
15:20 - How would Rich describe or categorise a chatbot?
16:15 - What makes something agentic then?
17:52 - Jason helps Rich understand what to expect from his exploration
18:51 - What's the relationship between goals and tasks?
20:06 - Rich explains what makes this so interesting for him and got him excited
26:12 - Empowering Agents with the Right Tools
27:47 - Understanding Tasks vs. Goals
28:45 - Breaking Down Tasks for Efficiency
29:44 - How much agency do agents have?
31:38 - Task Descriptions and Expected Outcomes
33:03 - Teams of agents vs teams of people and specialists vs generalists
35:48 - How does an agent decide what to do next and how does it know it has completed the task?
36:40 - Defining Quality in Agent Outputs
38:15 - MOAR testing concepts that have parallels with Rich's exploration
40:28 - The consequences of not being accurate enough with your backstory, expected output, tasks, etc
43:34 - What happens when agenticai is asked to achieve the same goal without changing anything about the backstory, expected output, tasks, etc?
45:40 - Challenges of Iteration and Learning
46:47 - What are max iterations and what does that remind Rich of?
47:40 - Vern wonders how important semantics is going to be and how Testers can contribute to this work
49:42 - Rich riffs on exploratory testing
51:02 - Exploratory Testing and Agentic Learning. What does the Tester's story look like in the context of an agentic system from the agent's perspective?
54:15 - Exploring Autonomy in AI Systems
56:57 - Evaluating AI Outputs and Task Design
58:21 - What happens if/when the context is left blank in these agentic systems?
01:00:49 - Soooo where do the humans fit in if agentic systems can doAllTheThings?
01:02:37 - Wrap up: Take 1 - Designing small targeted tests vs designing small targeted tasks
01:04:46 - Wrap up: Take 2 - Agents delegating tasks to other agents. Er... WTF?!
01:06:00 - Wrap up: Take 3 - How is Rich feeling about AI & AI tools?
01:09:45 - Wrap up: Take 4 - Testers ASSEMBLE! How we're going to contribute in a world of AI
In this episode of the Vernon Richards show, the hosts discuss their goals for the new year, reflecting on the past year and sharing strategies for achieving personal and professional aspirations. They emphasize the importance of journaling, creating structured routines, and building accountability through community support. The conversation also touches on the significance of intentional content consumption and the benefits of sharing progress publicly. Overall, the episode serves as a motivational guide for listeners looking to set and achieve their own goals in 2025.
Links to stuff we mentioned during the pod:
00:00 - Intro: New Year, New Goals
01:09 - Welcome
01:33 - Today's theme: Achieving our goals
03:29 - How are we approaching goal setting and achieving goals?
05:35 - Vernon describes the Yearly Review process he used
07:52 - Journalling as a means to remember what happened throughout the year
09:33 - Where else would journalling be useful?
11:20 - Rich talks about notebooks and how he uses writing to achieve his goals and remember his wins
12:58 - Rich's goals for 2025
15:30 - Timeblocking FTW!
16:39 - Starting small
18:23 - Vernon's goals for 2025
19:26 - Richard's reading goals and his library
24:15 - How to stay accountable: Building in public & Accountability buddies
31:34 - How to stay accountable: Bullet journal
34:21 - Vern shares the concept of "Look at me" vs "Look at this" content
39:10 - Rich realises why he hasn't done as much signal boosting as he used to
41:25 - How to stay accountable: Managing dopamine
44:55 - Managing focus by removing distraction
47:49 - Intention and finding a balance between resting vs procrastination and striving vs obsession
54:10 - How to stack the odds of success i
00:00 Introduction
02:00 Happy to be Employed
05:00 Vernon Wrote a Book
08:00 Talking at a Developer Conferences
16:20 PeersCon
20:24 Our Podcast
21:50 Agile Testing Days Experience
22:20 Our Podcast again
28:30 Bluesky
32:30 Vernon’s New Newsletter
41:00 Generalist Specialist and AI
51:00 Discipline and Consistency
54:00 Vernon’s Personal Reflection
55:40 Richard’s Personal Reflection
Links to stuff that we mentioned:
05:00 - Mark’s and Nicola’s Book - The Software Tester’s Journey
05:01 - Nicola Lindgren Bluesky Profile
08:00 - Richard’s talk at Oredev
08:00 - Øredev conference - https://oredev.org/
11:30 - Abby Bangser - Bluesky Profile
15:30 - Gitte Klitgaard - Bluesky Profile
16:20 - PeersCon - https://testingpeerscon.com/
18:24 - Beth Probert - https://www.linkedin.com/in/bethprobert/
18:48 - Testing Peers Podcast
21:20 - Our Agile Testing Days Podcast episode
21:46 - Agile Testing Days conference
29:00 - Tobias Geyer Bluesky
32:30 - Jit Gosai Bluesky
32:30 - JIt Gosai Quality Engineering Newsletter
This conversation captures the vibrant atmosphere of Agile Testing Days in Potsdam, highlighting the importance of community, targeted automated testing, and the exploration of tester identity. The hosts discuss their experiences at the conference, including workshops, networking opportunities, and a unique musical performance that showcased the talents of attendees. They delve into the significance of understanding tester identity and the symbols associated with it, emphasizing the need for connection and belonging within the testing community. This conversation at Agile Testing Days explores various themes including the experience of performing in a musical, insights from keynote speakers on technical coaching, the importance of documenting achievements for career advancement, and the evolving identity of professionals in agile environments. The discussion emphasizes the value of networking at conferences and the need for continuous learning and adaptation in one's career. [AI]
Links to stuff we mentioned during the pod:
01:00 - Intro LIVE from Agile Testing Days!
03:00 - Why are we here?
10:52 - The importance of networking and conferences
12:17 - What kind of event is ATD?
13:05 - The ATD Musical (you read that correctly)
18:29 - Guest: Señor Performo discussing who he is and performance testing
21:53 - Guest: Jenna Charlton explaining the relationship between testing, identity, and symbols
36:15 - Guest: Basti aka Bastian "Best Bad Boss Ever" Knerr talking about being part of the musical
39:05 - Guest: Baart Knack talking about his escapades at ATD over the years and hi...
#contentcreation #softwaretesting
In this conversation, Richard Bradshaw and Vernon discuss various themes including veganism, personal achievements, the writing process, and the importance of collecting ideas for content creation. They explore the significance of networking within the software testing community and reflect on the dynamics of social media, particularly Twitter and LinkedIn. The conversation also highlights the value of storytelling in professional settings and shares insights from a recent conference experience. In this conversation, Richard Bradshaw shares his experiences from the Husteth Conference, including the challenges and triumphs of being a closing keynote speaker. He discusses the unexpected power cut during his talk, the importance of engaging Q&A sessions, and the value of networking and building connections at conferences. The conversation emphasizes the significance of community, sharing insights, and the overall positive experience of attending events.
00:00 Introduction and Veganism Discussion
02:58 Celebrating Achievements and Book Launch
06:00 Writing Process and Content Creation
08:54 Collecting Ideas: The Fieldstone Method
11:55 Building in Public and Sharing Experiences
15:04 Networking and Community Engagement
17:58 Reflections on Social Media Dynamics
21:00 The Importance of Collecting Stories
23:55 Conference Experience and Innovations
26:53 Q&A Dynamics at Events
32:25 Reflections on the Husteth Conference
34:09 The Power Cut Incident
39:43 The Importance of Q&A Sessions
45:21 Closing Keynote Experience
49:42 Traveling and Networking at Conferences
52:22 Conversations and Connections at Events
57:11 Final Thoughts and Takeaways
In this episode of the Vernon Richard show, Richard and Vernon engage in an AMA format, discussing various topics including their collaborative projects, future aspirations, the impact of their quality testing mindset on daily life, memorable swag from testing events, experiences in uncomfortable establishments, significant learning moments, and the importance of testing environments. They emphasize the need for continuous content creation and the desire to connect with their audience for future interactions.
00:00 - Intro
00:16 - Ben's question: If you could do any co-lab with anyone from the community, who would it be, and what might it look like?
05:43 - Leigh's question: Where do you and vern see yourselves in 5 years, or want to be in 5 years, doing what kind of role in what kind of company?
15:46 - Andy's question: When I speak with people, I love hearing how their Quality/Testing mindset spills over into day to day life. One person used to test their childrens' toys by seeing if they could use them one-handed covered in olive oil. Another guy would occasionally test how far away his TV remote would work and see if it changes 😂
Maybe you've covered this stuff already, but personally I always love hearing about these funny quirks and testing 'life'.
26:05 - Emily's question: What's the best swag you've ever picked up from a testing event?
31:29 - Mark's question: Have you ever walked in to a pub that's so bad you want to instantly leave, But because of obligated politeness and fear of that awkward feeling of walking straight out again you go stayed?
35:08 - Ide's question: Looking back, best learning ever (at that moment perhaps biggest fail ever), with context, and what/when did it change from: Argh! to Ahhh!
40:53 - Anonymous question: Do you think one of your test environments should match the spec of production?
Links to stuff we mentioned during the pod:
The conversation revolves around the challenges faced by testers and the lack of understanding and support they receive from leadership. The hosts discuss the misconception of the value of testers and the need for leaders to create an environment where testers can thrive. They highlight the importance of addressing the frustrations and unhappiness of testers and the need for leaders to take responsibility for creating a supportive and nurturing culture.
The conversation also touches on the changing expectations of developers compared to testers and the need for leaders to have a better understanding of the role and value of testers. The conversation explores the disconnect between the expectations and perspectives of testing and quality engineers. It highlights the need for leaders to take responsibility for creating a supportive environment and culture. The role of tools and marketing in shaping these expectations is also discussed.
The conversation concludes with the importance of clear communication, understanding the needs of the team, and nurturing the growth of testers and quality engineers.
#podcast #softwaretesting #software #softwaredevelopment
Links to stuff we mentioned during the pod:
00:00 Introduction and Technical Discussion
01:27 - What's going on with Rich's fingers?!
01:36 Challenges and Misunderstandings Faced by Testers and Quality Engineers
01:54 - Everything the Testers in your team want to tell you but are too afraid
02:50 - Vern's theory
07:40 - Why do other roles get "the nutrients" they need?
08:09 The Value of Testers and the Need for Supportive Leadership
10:26 - What do leaders misunderstand about the value of Testers and QEs?
11:38 - Support networks Vs Challenger networks
12:09 - The bugs we report that people REALLY don't like!
12:43 - System problems disguised as testing problems
14:37 Shifting Expectations for Developers and the Evolving Understanding of Testing
14:53 - Groundhog day!
16:10 - Rich wonders if our expectations are reasonable
19:29 - How does the world perceive Developers, Designers, and Testers?
21:04 - How expectations have changed for Developers
23:07 Creating a Supportive and Nurturing Environment for Testers
24:08 - How a lack of curiosity impacts the wellbeing of your team
26:21 - Expectation vs Reality
26:59 Bridging the Gap: Expectations and Perspectives
27:27 - How to collaborate on expectations with the Tester in your life!
28:37 - Martin's crazy experiments, Glue Work, Technical Leadership, and Quality Engineering
30:13 - What does this tell us about the culture of the organisation?
30:58 Creating a Supportive Environment for Testers and Quality Engineers
31:52 - Rich asks if this is only a problem for people like us?
32:41 The Role of Tooling in Shaping Expectations
35:30 - What can we learn from the CEO/CTO relationship?
38:12 - What can we learn from relationships, period?
40:19 - ⚽️ Footy
42:16 - The impact of language and narrative on testing in the test tool market
45:50 - The link between testing, manual labour, and knowledge work
46:20 Advocating for Testers and Quality Engineers
47:10 - Hiring to solve problems or to put bums in seats
48:00 - Rich takes us back to the chicken and egg
50:08 - A potential new focus and name for the show!
51:22 - Outro
In this episode, Richard and Vernon discuss the topic of hiring and share their thoughts on the annoying things that companies and hiring managers do. They emphasize the importance of seeking clarification and understanding the context behind red flags on a candidate's CV.
They also discuss the power dynamic in the hiring process and provide advice for job seekers on how to mitigate potential problems. They highlight the value of storytelling and narrative in CVs and suggest cherry-picking relevant experiences to showcase in job applications.
In this conversation, Richard and Vernon discuss job hunting strategies and offer advice for those looking for new roles. They emphasize the importance of networking, building a personal brand, and being intentional about what you share on platforms like LinkedIn.
They also discuss the distinction between skills and tools in job specifications and CVs, encouraging a focus on transferable skills rather than specific tools. The conversation concludes with a call for feedback and suggestions from listeners.
#softwaretesting #software #hiring #hiringtips
Links to stuff we mentioned during the pod:
00:00 - Intro
00:49 - Let's talk about hiring
01:00 - Hiring managers annoying habits
01:43 - Vern's rant about "red flags" on CVs
03:59 - Rich explains why he thinks option C is reasonable (in the circumstances!)
05:30 - Hiring is like software development!
05:37 - Red flags == Bugs in production
06:42 - Red flags == Feature flags / AB tests
09:41 - A recruiter's perspective on the issue
12:15 - How Rich approached his recent job search
14:11 - Don't be passive during the interview: Asking questions, clarifications, and storytelling
15:30 - How to handle objections during an interview
16:36 - The importance of weaving the hidden gems of your experience into you interview
18:07 - How Labelling and Accusation Audits can help you in interviews
How to combine labelling and an accusation audits to your advantage in interviews
19:31 - Leverage your risk analysis skills to prep for your interview
20:30 - How to sell yourself short in an interview
23:20 - The meta skill of storytelling
24:49 - Storytelling with your CV
28:04 - Excellent advice about leveraging LinkedIn that Vern isn't following!
29:49 - Rich's advice about what information to include and Vern's mysterious friends' experience trying to take that advice
31:26 - Contradictory job hunting advice and how to swerve it
32:05 - The ultimate hack(s) for job hunting
36:10 - How do you decide or calculate what kind of material to include in your "personal brand"?
41:09 - The balance of serious vs fun content
43:01 - Rich questions who Vern chooses to hang out with
43:39 - How to share other people's ideas and yours at the same time
45:47 - Shout out to PastRich!
46:06 - Rich wants to talk about how we talk about skills
48:01 - Elizabeth Zagroba's interesting take on writing CVs
51:21 - Vern has an idea for the next episode
52:51 - What advice did we miss? Help!
In this conversation, Richard and Vernon discuss their use of AI in their lives and then explore the topic of working at their dream companies. Richard expresses his fascination with SpaceX and the incredible engineering and technology involved in space exploration. Vernon shares his love for video games and the art and science behind their creation.
They also touch on the emotions involved in software testing and how they can be clues to underlying problems. The conversation explores various emotions experienced during software testing, including frustration, joy, fear, suspicion, and familiarity. Frustration often arises when encountering bugs or issues, while joy can be felt when using a well-designed and user-friendly app. Fear is associated with the potential for irreversible actions or data loss. Suspicion arises when recognizing patterns or past experiences that may indicate potential problems. Familiarity helps in identifying missing features or inconsistencies.
The conversation also touches on the concept of behavior-driven development (BDD) and the importance of having conversations and automating them rather than just documenting them.
#exploratorytesting #softwaretesting #testing #software #softwaredevelopment #emotions
00:00 - Intro attempt no. 1
00:50 - Intro attempt no. 2
01:16 - ⚽️ Footy
01:46 - ⚽️ Footy related preamble to the question
03:01 - Dream job question
03:36 - Space! The final frontier!
03:54 Dream Job: Working at SpaceX and Developing Software for Rockets
08:30 - Dream job: Nintendo, adventure games, and storytelling
11:54 The Fascination with Rockets and Space
17:04 - Emotions in software testing
19:41 Beyond Functionality: The Importance of User Experience and Emotions
20:10 The Role of Emotions in Software Testing
20:35 Using Frustration and Anger as Indicators of Improvement Areas
21:29 Learning and Coding: Frustration and Joy
22:36 BDD and Sweary Outbursts
23:56 The Importance of Clear User Scenarios
25:34 The Value of Conversations in BDD
26:50 - Joyful testing
28:57 Fear and Suspicion in Testing
31:14 The Anxiety of Sending Money
33:27 - Suspicion and that feeling of de ja vu
36:09 Applying Past Experiences and Patterns
37:25 The Evolution of Suspicion and Familiarity
39:27 The Role of Heuristics in Testing
41:24 The Absence of Joy in Testing
42:46 Emotions as a Guide for Testing Strategies and Approaches
Links to stuff we mentioned during the pod:
