#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 Discussion02:58 Celebrating Achievements and Book Launch06:00 Writing Process and Content Creation08:54 Collecting Ideas: The Fieldstone Method11:55 Building in Public and Sharing Experiences15:04 Networking and Community Engagement17:58 Reflections on Social Media Dynamics21:00 The Importance of Collecting Stories23:55 Conference Experience and Innovations26:53 Q&A Dynamics at Events32:25 Reflections on the Husteth Conference34:09 The Power Cut Incident39:43 The Importance of Q&A Sessions45:21 Closing Keynote Experience49:42 Traveling and Networking at Conferences52:22 Conversations and Connections at Events57: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 - Intro00: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:00:16 - Stuff from Ben's questionButch MayhewButch's websiteButch's LinkedInBen DowenBen's LinkedInLisi HockeLisi's blogLisi's LinkedInNicola LindgrenNicola's YouTube channelNicola's blogThe book we're writing called "The Tester's Journey"!Nicola's first book "Starting Your Software Testing Career"!Nicola's LinkedInKaren ToddKaren's YouTube channelKaren's LinkedInDean MoonDean's websiteDean's LinkedInAsh Coleman HynieAsh's new product CountrPT!Ash's LinkedInKelsey HightowerKelsey's X (formerly Twitter) accountManchester Tech FestivalTheir websiteTheir founder Amy NewtonEmily O'ConnorEmily's LinkedInDorothy "Dot" GrahamDorothy's LinkedInJanet GregoryJanet's websiteJanet's LinkedInAbby BangserAbby's LinkedInMelissa EadenMel's blogMel's LinkedInStuff from Leigh's questionLeigh RathboneLeigh's LinkedInAlan PageAlan's newsletterAlan and Brent's podcastAlan's LinkedInThe Black Tech Unplugged Podcast hosted by Deena McKayNB (from Vernon): I got the name of the podcast wrong 🤦🏾♂️! I mentioned the Tech Is The New Black podcast, which is awesome but crucially, NOT the one Deena creates. Forgive me Deena 🙏🏾.The Quality Bits podcast hosted by Lina ZubyteNB (from Vernon): I blundered AGAIN 🤦🏾♂️! The name of the pod is Quality Bits, BITS! Not Bytes. Good grief. Sorry Lina 🙏🏾Daniel KnottDaniel's YouTube channel (with 107,000 subscribers at the time of writing 🤯)Daniel's blogDaniel's booksHands-On Mobile App Testing on LeanpubSmartwatch App Testing on LeanpubDaniel's LinkedInJoe ColantonioJoe's YouTube (with 387,000 subscribers at the time of writing 🤯)Joe's websiteStuff from Andy's questionAndy JohnsonAndy's LinkedInDel DewarDel's blogDel's PS5 botDel's LinkedInStuff from Emily's questionEmily O'ConnorEmily's LinkedInStuff from Mark's questionMark GillottMark's LinkedInStuff from Ide's questionIde KoopsIde's LinkedInStuff from the Anonymous questionChristian LeggetChristian's LinkedInJonathan MarshallJonathan's LinkedIn
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:11:38 - Challenge Networks. Listen to Adam Grant explain the concept of a Challenge Network on the DOAC podcast.26:30 - Jerry Weinberg's 2nd Law of Consulting from his book The Secrets of Consulting"No matter how it looks at first, it's always a people problem."Find more of Jerry's quotes on this page28:40 - Vern talking about his talk in episode 6 "How No-Code Test Tools, Technical Leadership & Glue Work Impact Software Quality"Tanya's Glue Work presentation which you can read or watch"What Is Quiet Quitting?" a BBC News article describing the phenomenonVernon's Agile Yorkshire presentation where he describes the link between those concepts29:19 - Martin HynieMartin describing the wider impact of his talkMartin's LinkedIn30:59 - Maaret Pyhäjärvi & Anna BaikAnna's quote that Maaret shared on LinkedInAnna's LinkedInMaaret's LinkedIn34:35 - Prompt EngineerWhat's a Prompt Engineer?35:30 - Adelina ChalmersAdelina's AMA session that I joined (please follow her and join her sessions, she's AWESOME!)Adelina's LinkedIn00:00 Introduction and Technical Discussion01:27 - What's going on with Rich's fingers?!01:36 Challenges and Misunderstandings Faced by Testers and Quality Engineers01:54 - Everything the Testers in your team want to tell you but are too afraid02:50 - Vern's theory07:40 - Why do other roles get "the nutrients" they need?08:09 The Value of Testers and the Need for Supportive Leadership10:26 - What do leaders misunderstand about the value of Testers and QEs?11:38 - Support networks Vs Challenger networks12:09 - The bugs we report that people REALLY don't like!12:43 - System problems disguised as testing problems14:37 Shifting Expectations for Developers and the Evolving Understanding of Testing14:53 - Groundhog day!16:10 - Rich wonders if our expectations are reasonable19:29 - How does the world perceive Developers, Designers, and Testers?21:04 - How expectations have changed for Developers23:07 Creating a Supportive and Nurturing Environment for Testers24:08 - How a lack of curiosity impacts the wellbeing of your team26:21 - Expectation vs Reality26:59 Bridging the Gap: Expectations and Perspectives27:27 - How to collaborate on expectations with the Tester in your life!28:37 - Martin's crazy experiments, Glue Work, Technical Leadership, and Quality Engineering30:13 - What does this tell us about the culture of the organisation?30:58 Creating a Supportive Environment for Testers and Quality Engineers31:52 - Rich asks if this is only a problem for people like us?32:41 The Role of Tooling in Shaping Expectations35:30 - What can we learn from the CEO/CTO relationship?38:12 - What can we learn from relationships, period?40:19 - ⚽️ Footy42:16 - The impact of language and narrative on testing in the test tool market45:50 - The link between testing, manual labour, and knowledge work46:20 Advocating for Testers and Quality Engineers47:10 - Hiring to solve problems or to put bums in seats48:00 - Rich takes us back to the chicken and egg50: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:01:43 - Vernon's LinkedIn post about how NOT to handle "red flags" spotted on CVs!09:41 - Wayne Bennett, FRSA, CertRPWayne's comment on my postWayne's recruitment firm Made4Tech GlobalWayne's LinkedIn17:47 - Recruiters we think are awesome!Wayne Bennet's LinkedIn (particularly for Manchester and NW England roles)Kelli Jackson's LinkedIn (for North American roles and runs a community for midlifers changing careers)Gabbi Trotter's LinkedIn (UK wide but particularly the North West and Midlands roles)Samir Mehta's LinkedIn (although he's internal now & works with Rich the poor guy)Jamie Doyle's LinkedIn (UK wide and a legend)Kristina Javůrková's LinkedIn (for Benelux roles)Matt Drinkwater's LinkedIn (UK wide and hosts QE Babble)James Duke's LinkedIn (UK wide and lover of fast cars)18:07 - Book: Never Split The Difference by Chris VossAn explanation of LabellingAn explanation of an Accusation AuditChris's websiteGrab the book from Amazon23:53 - Huib SchootsHuib's websiteAnd Huib is one of the folks I've heard talk about storytelling! You can find that presentation here.Huib's LinkedIn32:28 - Alan RichardsonAlan's websiteAlan's Patreon communityAlan's LinkedIn43:01 - The Quality Talks PodcastThe Quality Talks podcast hosted by Stu and ChrisStu's LinkedInChris's Linkedin48:01 - Elizabeth ZagrobaElizabeth's article Doubt Builds TrustWhich contains an example of a Trustworthy CVElizabeth's websiteElizabeth's LinkedIn53:18 - The Never Search Alone movement00:00 - Intro00:49 - Let's talk about hiring01:00 - Hiring managers annoying habits01:43 - Vern's rant about "red flags" on CVs03: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 production06:42 - Red flags == Feature flags / AB tests09:41 - A recruiter's perspective on the issue12:15 - How Rich approached his recent job search14:11 - Don't be passive during the interview: Asking questions, clarifications, and storytelling15:30 - How to handle objections during an interview16:36 - The importance of weaving the hidden gems of your experience into you interview18:07 - How Labelling and Accusation Audits can help you in interviewsHow to combine labelling and an accusation audits to your advantage in interviews19:31 - Leverage your risk analysis skills to prep for your interview20:30 - How to sell yourself short in an interview23:20 - The meta skill of storytelling24:49 - Storytelling with your CV28: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 advice31:26 - Contradictory job hunting advice and how to swerve it32:05 - The ultimate hack(s) for job hunting36: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 content43:01 - Rich questions who Vern chooses to hang out with43:39 - How to share other people's ideas and yours at the same time45:47 - Shout out to PastRich!46:06 - Rich wants to talk about how we talk about skills48:01 - Elizabeth Zagroba's interesting take on writing CVs51:21 - Vern has an idea for the next episode52: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. 100:50 - Intro attempt no. 201:16 - ⚽️ Footy01:46 - ⚽️ Footy related preamble to the question03:01 - Dream job question03:36 - Space! The final frontier!03:54 Dream Job: Working at SpaceX and Developing Software for Rockets08:30 - Dream job: Nintendo, adventure games, and storytelling11:54 The Fascination with Rockets and Space17:04 - Emotions in software testing19:41 Beyond Functionality: The Importance of User Experience and Emotions20:10 The Role of Emotions in Software Testing20:35 Using Frustration and Anger as Indicators of Improvement Areas21:29 Learning and Coding: Frustration and Joy22:36 BDD and Sweary Outbursts23:56 The Importance of Clear User Scenarios25:34 The Value of Conversations in BDD26:50 - Joyful testing28:57 Fear and Suspicion in Testing31:14 The Anxiety of Sending Money33:27 - Suspicion and that feeling of de ja vu36:09 Applying Past Experiences and Patterns37:25 The Evolution of Suspicion and Familiarity39:27 The Role of Heuristics in Testing41:24 The Absence of Joy in Testing42:46 Emotions as a Guide for Testing Strategies and ApproachesLinks to stuff we mentioned during the pod:00:09 - KrispKrisp.ai - Noise cancelling software (not an affiliate link!)00:56 - Tristan LombardTristan's LinkedInTristan's TwitterVincent Kompany03:36 - SpaceX07:02 - Virgin GalacticTheir websiteHistoric mission which included the first women astronauts from the CaribbeanAntogua08:34 - Nintendo09:50 - Wonder Boy III: The Dragon's TrapWonder Boy III: The Dragon's Trap wiki page10:44 - The Zelda gamesThe Legend of Zelda: A Link to the Past wiki page12:49 - Daniel KnottDaniel's YouTube channelDaniel's blogDaniel's booksHands-On Mobile App Testing on LeanpubSmartwatch App Testing on LeanpubDaniel's LinkedIn22:45 - Behaviour Driven DevelopmentWhat is BDD? Doc page on cucumber.ioAnd again on the wiki page24:59 - Mark WinteringhamMark's website and blogMark's LinkedIn25:43 - Liz Keogh"Having the conversation > Documenting the conversation > Automating the conversation" Check out Slide 14 of Liz's excellent course Behaviour Driven Development38:40 - Beren van DaeleBeren's Testsphere cards (including links where you can buy your own deck - RECOMMEND!)The RiskStorming process based on the Testsphere deck for discovering risks (including using emotions!)Beren's websiteBeren's LinkedIn
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 & Mentions01:01 - CrowdstrikeWho are they?This is their wikipedia pageThis is their About us page01:17 - What is a kernel?01:56 - What happened?BBC article - Crowdstrike release causes "Mass IT outage affects airlines, hospitals, media and banks"Preliminary Post Incident Review from Crowdstrike05:32 - Dave's garage explanation of what happened 😙🤌🏾 (Ex-Microsoft Dev)12:46 - Rich's LinkedIn posted about jumping to conclusions in the wake of the Crowdstrike issue15:38 - Mark WinteringhamMark's website and blogMark's excellent blog post about "Quality Engineering, Digital Employees and Job Security"Mark's LinkedIn28:00 - Article: Crowdstrike CEO called to congress37:59 - Crowdstrike updatesTheir blogTheir Remediation and Guidance Hub: Falcon Content Update for Windows HostsTheir Preliminary Post Incident Review (PIR): Content Configuration Update Impacting the Falcon Sensor and the Windows Operating System (BSOD)44:47 - Dame Anita FrewWho is Dame Anita Frew?00:00 Introduction and Appreciation for Listeners00:33 - Did anything interesting happen in the last week?01:01 - Crowdstrike (what else?!)01:56 - Vernon & Richard describe what happened with the Crowdstrike shenanigans04:23 Realizing the Global Impact of the Outage06:16 Explaining the Kernel Bug and its Effects07:44 The Process of Getting a Kernel-Based Application08:40 The Kernel's Response to Errors and Risks09:29 The Significance of the Kernel in Software10:35 Updates and News from CrowdStrike11:11 The Importance of Software Testing and Quality12:12 The Fallacy of Blaming Testers and Testing12:46 - Vern reads out Rich's LinkedIn post in the immediate wake of the issue14:29 Recognizing Process Shortcomings and Risks15:38 - The danger of "hot takes"16:24 Taking Ownership and Learning from Mistakes19:15 - Common Crowdstrike Hot Takes: Thou shalt not release of Friday!19:46 Alternative Explanations and Hot Takes21:16 The Danger of Treating Hot Takes as Facts22:20 The Debate Around Releasing on Fridays23:17 Mitigating Risks and Context-Specific Decision-Making24:42 The Need for Continuous Improvement and Learning26:18 - Common Crowdstrike Hot Takes: Clearly this hasn't been tested!26:37 - Common Crowdstrike Hot Takes: Obvious risk mitigation steps the should have taken28:00 - Crowdstrike CEO called to congress28:45 The Impact of Software Bugs and the Importance of Quality30:54 - What might have happened if Crowdstrike didn't release a critical update?36:22 Mitigating Risks and Turning Off Software in Critical Situations37:59 - Updates directly from Crowdstrike38:39 - Rich's Columbo question43:48 - The miracle of ubiquitous software45:42 The Response of CrowdStrike and the Potential Human Impact46: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 - Intro01: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 FailLinks to stuff we mentioned during the pod:07:50 - AI, Generative AI and Large Language Models (LLMs)Useful material:Microsoft course AI for Beginners07:50 - Dr Tariq KingTariq's LinkedIn07:50 - Melissa EadenMelissa's LinkedIn09:52 - The book AI-Assisted Testing by Mark WinteringhamGrab the book hereMark's websiteMark's LinkedIn10:53 - Knowledge workOur previous discussion on Knowledge Work in Episode 1A definition of knowledge work from Wikipedia13:59 - Vernon's Scripting Vs Exploring workshop he delivered at the European Testing Conference (ETC)14:03 - ETC (organised by Maaret Pyhäjärvi) is now sadly on hiatus27:26 - Doug Hoffman and High Volume Automated Testing (HiVAT)An explanation of HiVAT by Cem KanerDoug's LinkedIn33:25 - The Agile Yorkshire meetup organised by Royd BrayshayThe Agile Yorkshire websiteRoyd's LinkedIn33:59 - Cassandra H. LeungCassandra's blogCassandra's LinkedIn34:22 - Tanya ReillyTanya's websiteTanya's Glue Work presentation which you can read or watchTanya's LinkedIn37:22 - "What Is Quiet Quitting?" a BBC News article describing the phenomenon38:23 - Jenna CharltonJenna's LinkedInThe presentation I referred to is called: "Imperfect Agile: Lessons Learned From Embracing The Journey And Ditching The Rules". It was great and I'll see if Jenna is willing and able to share a link to it as soon as I can🙂39:17 - Stuart DayStu's Quality Talks podcast that he co-hosts with Chris HendersonStu's LinkedInChris's Linkedin43:30 - Anna BaikAnna's LinkedInAnna's quote that Maaret shared on LinkedIn
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:01:42 - Joëlle BurkhardtJoëlle's LinkedIn06:41 - James ThomasJames' one liner on his blogJames' LinkedIn09:15 - AJ WilsonAj's LinkedIn14:32 - Kelsey's story about relating the impact of software problems to real humans15:10 - Mark GillottMark's LinkedIn15:34 - Template letter for banning pineapple on pizza17:10 - Olivier BanalOlivier's LinkedIn18:25 - Leigh RathboneLeigh's LinkedIn22:30 - Deb SherwoodDeb's LinkedIn22:42 - Jerry WeinbergJerry's Wikipedia page (his books are highly recommended)23:46 - Joep SchuurkesJoep's blogJoep's LinkedIn28:36 - Mark TomlinsonMark's websiteMark's podcastMark's LinkedIn32:45 - Anna RoyzmanAnna's LinkedIn38:42 - Melissa FisherMelissa's LinkedIn38:42 - In case you need to know what the TARDIS is, please read this!40:59 - David Goggins (definitely watch/listen to his stuff with headphones on or with no kids around because 🤬)David's cookie jar philosophyDavid's website43:47 - End of year reflection resourcesDickie Bush & Nicolas Cole's Yearly Review Process00:00 - Intro01: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 AILinks to stuff we mentioned during the pod:00:00 - James ThomasJames' blogJames LinkedIn02:42 - The Testing Atelier ConferenceTheir websiteTheir YouTube channel05:10 - Jit Gosai Jit's Leeds Testing Atelier postJit's Leeds Testing Atelier talkJit's blog Jit's Quality Engineering Newsletter Jit's LinkedIn05:43 - Elly GausdenElly's LinkedIn08:03 - The Battleships board game09:00 - The Colt Express board game11:02 - Clare NormanClare's LinkedIn11:44 - Lego Serious Play Training11:56 - Rich's Lego Automation workshop13:33 - Elliot ThurlandElliot's talkElliot's LinkedIn13:38 - The Post Office Horizon scandalThe public enquiry websiteArticle on Wikipedia13:53 - James ChristieJames' blogJames' body of work regarding the Post Office scandal16:30 - BBC Radio 4 series about the Post Office Scandal16:35 - 4 part television drama for ITV17:48 - The Nightmare Headline game is described in Elisabeth Hendrickson's excellent book Explore It!18:43 - Bug AdvocacyThe Association for Software Testing (AST) flavour of the courseThe Black Box Software Testing training programs in collaboration with Altom and Cem Kaner19:20 - Kelsey HightowerKelsey's Twitter/XKelsey's GitHub21:08 - Leah King & Tracy ArchibaldTheir talkLeah's LinkedInTracy's LinkedIn23:44 - Emily O'ConnorEmily's LinkedIn28:20 - Steven MilneSteven's talkSteven's LinkedinSteven's Twitter/X34:54 - Paul ColesPaul's LinkedIn34:54 - Rita AvotaRita's LinkedIn35:20 - How assistive technology is REALLY usedAccessibility Testing with People with Disabilities - Samuel ProulxWe've linked to the specific part of the video that shows the demo but we'd recommend watching the whole presentation!38:47 - Colin WrenColin's talkColin's LinkedIn45:24 - Melissa RocksMelissa's talkMelissa's LinkedInMelissa's Twitter/X51:14 - Spoon Theory56:03 - Ian ThomasIan's LinkedIn56:29 - Rich's "allergic reaction" presentation: "Pyramids Are Ancient - Test Automation Strategy"59:45 - The Adobo & Avocados show01:01:52 - Kiel GoodmanKiel's LinkedIn01:04:45 - The Gartner Hype Cycle01:04:59 - Troy MagennisTroy's websiteTroy's LinkedIn00: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 episode04: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 Feedback09:01 Creating Clear and Compelling Abstracts16:21 The Importance of Actionable Feedback33:10 The Power of Networking45:33 Finding the Balance: Asking for Help vs. Helping Yourself53:06 The Importance of Continuous LearningLinks 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 LinkedIn13:00 - Clear not clever explained by Nicolas Cole17: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 page27:00 - Abby Bangser on LinkedIn27:30 - Ash Coleman Hynie on LinkedIn31:30 - Vernon Scott II on LinkedIn34:00 - Marie Cruz and Lewis Prescott's book 45:47 - Lisi Hocke's website & Ben Dowen website46:08 - My old pal 49:55 - The First 90 Days book on Amazon56:37 - What's AWS? 58:50 - What about Google Cloud? 58:51 - What's Heroku?
The second episode of the Vernon Richard show discusses the PeersCon conference and highlights some of the key talks. Topics covered include the concept of minimal shippable risk, the importance of psychological safety in creating a productive work environment, the challenges and learnings of stepping into a leadership role, and the role of DevOps in organisations.We express our appreciation for the speakers and their valuable insights. The conversation covered various themes, including the importance of embracing DevOps and the role of testers in the process. The concept of glue work, which involves technical leadership and ensuring collaboration and success, was discussed. The negative impact of debates on LinkedIn and the need for respectful and curious engagement were highlighted. The importance of framing conversations and choosing the right medium for discussions was emphasized. The idea of thinking like a scientist and valuing getting right over being right was also explored.* Generated by AI.00:00 - Introduction00:47 - Our overall thoughts about the inaugural PeersCon event03:00 - Heather Reid's presentation "Wait! That's not tested"12:05 - Jit Gosai's presentation "Psychological safety – The link between speaking up, complexity and high performing teams"16:48 - Al Goodall's presentation "Things I Learned being a new(ish) Quality Manager"20:43 - Beth Clarke's presentation "Being the Glue: The Role DevOps in Testing"26:38 - Leigh Rathbone's presentation "The history of testing and why its important as it feeds our future"27:44 - Debates on LinkedIn32:05 - Choosing the right medium for sharing ideas and managing your energy35:04 - The challenges of online debate39:44 - Preachers, Prosectors, Politicians and thinking like a ScientistLinks to stuff we mentioned during the pod:00:32 - The PeersCon website02:28 - The Testing Peers podcast 03:00 - Heather Reid Heather's blog Heather's LinkedIn07:55 - Vernon's Quality Coaching Kickstart Guide 12:05 - Jit Gosai Jit's blog Jit's Quality Engineering Newsletter Jit's LinkedIn16:48 - Al Goodall Al's blog Al's LinkedIn20:43 - Beth Clarke Beth's blog Beth's LinkedIn22:33 - "First time?" meme from Maaike Brinkhof 23:39 - Tanya Reilly Glue Work26:38 - Leigh Rathbone Leigh's LinkedIn29:50 - Testing vs Checking30:02 - Context Driven Testing30:18 - Caleb CrandallCaleb's great post about mindset Caleb's LinkedIn 33:05 - James Bach James' blog 39:06 - Vernon explaining Coaching and being 2% right on Deena McKay's Black Tech Unplugged podcast39:24 - Adam Grant explaining Preachers, Prosectors, Politicians and thinking like a Scientist on the Diary of a CEO podcast
In this episode, Vernon and Richard introduce their new podcast and discuss the concept of smoke testing and knowledge work. They explain that smoke testing is a quick test to determine if something is alive or valid, often used when deploying new builds or testing in production. They also discuss the challenges of testing in production and the importance of health checks. In regards to knowledge work, they define it as cognitive work that involves manipulating and processing information based on expertise. They reflect on the recent arguments and discussions on LinkedIn and emphasize the need for nuance and understanding in these conversations.The conversation explores the challenges and misconceptions surrounding knowledge work in the context of software testing and automation. The speakers discuss how the intellectual effort and expertise involved in testing are often overlooked or undervalued. They highlight the importance of specialised knowledge, innovation, problem-solving, and continuous learning in testing. The conversation also touches on the perception of automated tests and the need to strike a balance between explicit test cases and exploratory testing.Yes, we are trying to keep this lean, and the above was generated by AI.00:00 Introducing the Vernon Richard Show04:47 Exploring the Concept of Smoke Testing14:32 Understanding Knowledge Work16:33 Introduction to Knowledge Work17:11 Defining Knowledge Work18:03 Characteristics of Knowledge Work19:22 Perception of Testing as Knowledge Work24:29 Perception of Programming as Knowledge Work27:48 Challenges in Communicating Testing Work31:05 Automated Tests as Test Case 2.034:46 Balancing Test Cases and Exploration35:56 Conclusion and Call for FeedbackLinks to stuff we mentioned during the pod:16:17 - Same as Ever by Morgan Housel: https://www.amazon.co.uk/Same-Ever-Timeless-Lessons-Opportunity/dp/B0CMQRQS33/16:29 - Morgan Housel on DOAC: https://youtu.be/vOvLFT4v4LQ?si=GU2pW-d9thmmFV4E27:21 - Huib Schoots: Telling The Testing Story: https://www.huibschoots.nl/storytelling/