By Vernon Richards and Richard Bradshaw
The podcast currently has 12 episodes available.
#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:
The conversation discusses the CrowdStrike outage caused by a kernel bug in a Windows update. The impact of the outage was widespread, affecting airports, medical professionals, banking, and even news channels.
The hosts emphasize the need to understand the complexity of software testing and not jump to conclusions or blame testers. They highlight the importance of continuous improvement, learning from mistakes, and taking ownership of problems.
The conversation also touches on the debate around releasing software on Fridays and the need for context-specific decision-making. The conversation explores the impact of software bugs and the importance of quality in software development. It discusses the ability to turn off software in critical situations, the challenges of working on low-level or embedded software, and the need for risk mitigation.
The conversation also touches on the response of CrowdStrike to the recent software bug and the potential human impact of such incidents. The concept of quality in software is examined, and the conversation concludes with a discussion on the increasing prevalence of software in various industries.
Links & Mentions
00:00 Introduction and Appreciation for Listeners
00:33 - Did anything interesting happen in the last week?
01:01 - Crowdstrike (what else?!)
01:56 - Vernon & Richard describe what happened with the Crowdstrike shenanigans
04:23 Realizing the Global Impact of the Outage
06:16 Explaining the Kernel Bug and its Effects
07:44 The Process of Getting a Kernel-Based Application
08:40 The Kernel's Response to Errors and Risks
09:29 The Significance of the Kernel in Software
10:35 Updates and News from CrowdStrike
11:11 The Importance of Software Testing and Quality
12:12 The Fallacy of Blaming Testers and Testing
12:46 - Vern reads out Rich's LinkedIn post in the immediate wake of the issue
14:29 Recognizing Process Shortcomings and Risks
15:38 - The danger of "hot takes"
16:24 Taking Ownership and Learning from Mistakes
19:15 - Common Crowdstrike Hot Takes: Thou shalt not release of Friday!
19:46 Alternative Explanations and Hot Takes
21:16 The Danger of Treating Hot Takes as Facts
22:20 The Debate Around Releasing on Fridays
23:17 Mitigating Risks and Context-Specific Decision-Making
24:42 The Need for Continuous Improvement and Learning
26:18 - Common Crowdstrike Hot Takes: Clearly this hasn't been tested!
26:37 - Common Crowdstrike Hot Takes: Obvious risk mitigation steps the should have taken
28:00 - Crowdstrike CEO called to congress
28:45 The Impact of Software Bugs and the Importance of Quality
30:54 - What might have happened if Crowdstrike didn't release a critical update?
36:22 Mitigating Risks and Turning Off Software in Critical Situations
37:59 - Updates directly from Crowdstrike
38:39 - Rich's Columbo question
43:48 - The miracle of ubiquitous software
45:42 The Response of CrowdStrike and the Potential Human Impact
46:22 - One Final Hot Take from Rich
In this conversation, Richard and Vernon discuss the need for manual test cases and manual testing in the future, particularly in the context of the rise of no code automation and AI.
They explore the underlying skills and activities involved in testing, such as critical thinking, analysis, communication, and understanding oracles and heuristics. They also touch on the importance of context and problem-solving in determining the appropriate testing approach. The conversation highlights the value of automation as a means to offload effort and gather information, rather than as an end in itself. In this conversation, Richard and Vernon discuss the importance of automation in testing and how it helps confirm the tester's knowledge of the system.
They also explore the concepts of glue work, quiet quitting, and quality engineering. Vernon shares his upcoming talk on setting quality engineers up for success and the challenges they face in organisations. They discuss the positioning of testers and the need for a cultural shift towards quality engineering. They invite listeners to share their thoughts and feedback on the topics discussed.
00:00 - ⚽️ Footy (1 min)
00:39 - Intro
01:54 - How will low-code and no-code automation tools impact the need for manual testers and manual test cases?
07:50 - How does Generative AI and/or Large Language Models (LLMs) change the answer?
20:39 - Issac Asmimov tangent!
21:18 - SPOILER ALERT! PLEASE SKIP IF YOU DON'T WANT TO HEAR ABOUT THE INCREDIBLE ISAAC ASIMOV STORY "PROFESSION" (I HOPE BECAUSE YOU'RE GOING TO READ IT YOURSELF!)
24:27 - SPOILER END!!!
33:07 - Vernon's talk: How We're Setting Up QEs To Fail
Links to stuff we mentioned during the pod:
In this episode, Vernon and Richard answer questions from their audience. They discuss what they would do if they weren't in software testing, the primary mission of a tester, advice for their younger selves, their stance on pineapple on pizza, and their preferences as trainers, mentors, consultants, and coaches. In this conversation, Vernon and Richard discuss various topics related to testing and quality.
They explore the meaning of quality and how it can vary depending on the context and individual perspectives. They also discuss the importance of testing and whether there are situations where testing may not be necessary. Additionally, they delve into the concept of a testing mindset and whether it is something that individuals are born with or can be developed. Finally, they reflect on what advice they would give to their younger selves, focusing on the themes of confidence, self-kindness, and self-care.
Links to stuff we mentioned during the pod:
00:00 - Intro
01:42 - Joëlle Burkhardt: What would you do if you weren't in software testing?
06:41 - James Thomas: You have to summarise what a tester's primary mission for a team is in a snappy one-liner that applies across contexts. What's your one-liner?
09:15 - Aj Wilson: What advice would you give the version of yourself, that was 2 years into software testing if you could, what would older wiser Richard advise new blood Richard?
15:10 - Mark Gillott: Why is pineapple on pizza still not illegal?
18:25 - Leigh Rathbone: What do you prefer, being a trainer (providing instruction and direction), a mentor, a consultant, or a coach?
22:30 - Deb Sherwood: What does quality mean for you?
28:36 - Mark Tomlinson: To test, or not to test.
32:45 - Anna Royzman: Testing mindset - are you born with it?
38:42 - Melissa Fisher: If you could jump in a tardis and go back in time, what would you tell your younger self?
In this episode of the Vernon Richard Show, Vernon and Richard discuss alternative names for the show and reflect on their recent activities. They talk about the Leeds Testing Atelier conference and highlight some of the workshops and talks they attended. They discuss the importance of play in the workplace and the impact of bugs in software development. They also mention the Post Office Horizon scandal and the need to consider the human impact of software failures.
The conversation covered various topics including testing chatbots, the importance of accessibility and user flow mapping. The speakers discussed their experiences with chatbots, highlighting both positive and negative interactions. They also talked about the significance of screen readers and the need for proper web app design to improve accessibility. User flow mapping was mentioned as a useful technique for building a joint team understanding of work tasks. The conversation also touched on the challenges of communication with anxiety and the benefits of being open about mental health in the workplace.
Various other topics were also discussed including reducing anxiety in the workplace, the concept of spoon theory, and the balance between speed and quality in software development. The speakers discussed the importance of building relationships and understanding how to communicate effectively to reduce anxiety. They also explored the idea of spoon theory, which relates to managing energy levels and prioritizing tasks. Lastly, they delved into the challenge of achieving both speed and quality in software development, emphasizing the need for a learning mindset and continuous improvement.
Description Generated by AI
Links to stuff we mentioned during the pod:
Troy's LinkedIn
00:00 - Banter (new name suggestions from James Thomas)
01:09 - The actual intro 😅
01:55 - Footy content warning 🚨
02:42 - What we intend to cover during this episode
04:42 - ⚽️ Footy (1 min)
05:10 - Jit's post about Leeds Testing Atelier
In this conversation, Richard and Vernon discuss the experience of being rejected for conference talks and the importance of actionable feedback. They emphasize the need for clear and compelling abstracts, as well as the value of networking and building relationships within the industry. They encourage individuals to continue sharing their stories and knowledge through alternative platforms such as YouTube, blogs, and meetups.
The conversation also touches on the power of diversity in conference lineups and the importance of providing opportunities for underrepresented voices. In this conversation, Richard and Vernon discuss the importance of networking and building relationships in the software testing industry. They emphasize the value of nurturing connections and being present in the network, rather than only reaching out when you need something.
They also discuss the challenges of onboarding onto a new team and share their experiences and strategies for effective onboarding. They highlight the importance of asking for help, sharing knowledge, and finding the right balance between asking for help and helping yourself. Overall, the conversation emphasises the power of relationships and continuous learning in the testing profession.
00:00 Introduction and Positive Feedback
09:01 Creating Clear and Compelling Abstracts
16:21 The Importance of Actionable Feedback
33:10 The Power of Networking
45:33 Finding the Balance: Asking for Help vs. Helping Yourself
53:06 The Importance of Continuous Learning
Links to stuff we mentioned during the pod:
08:00 - Richard's legendary advice about how to structure your conference proposal
10:07 - Sarah Deery on LinkedIn
13:00 - Clear not clever explained by Nicolas Cole
17:09 - Posts from Lena, Emna, and Jenna
20:00 - The Mash Program
20:20 - I couldn't find anything about Speak Easy but you can find the founder Anne-Marie Charrett
25:21 - Lisa Crispin's website and LinkedIn page
27:00 - Abby Bangser on LinkedIn
27:30 - Ash Coleman Hynie on LinkedIn
31:30 - Vernon Scott II on LinkedIn
34:00 - Marie Cruz and Lewis Prescott's book
45:47 - Lisi Hocke's website & Ben Dowen website
46:08 - My old pal
49:55 - The First 90 Days book on Amazon
56:37 - What's AWS?
58:50 - What about Google Cloud?
58:51 - What's Heroku?
The podcast currently has 12 episodes available.