Hobbies and personal interests can reveal valuable insights about personality traits, and people should be careful not to jump to conclusions based on the activities listed on a resume. A balance between curiosity, data analysis, and a desire to optimize and understand systems is key to a successful testing philosophy.

Testing is often seen as a personal hobby, not just a profession, and is driven by a need to improve systems, not just break them.

The Testing Peers

The Testing Peers - panel discussions about testing. Usually Chris Armstrong, Simon Prior, Russell Craxford and David Maynard, with occasional special guests. Show notes on the website have an episode description and resource links.

• https://testingpeers.com/
• https://www.youtube.com/playlist?list=PLgToaFvlUC7mruBdL9eQDS3WFcpg9ooeI

Episode Details

• Show Notes: N/A
• Published: 2026-02-23T15:00:00Z
• Duration: 2409
• Author: Testing Peers

Overview

The podcast examines how engaging in hobbies can positively impact professional work in testing and software development by cultivating creativity, storytelling, and teamwork. It explores hobbies like pro wrestling, Dungeons and Dragons, and gaming, emphasizing the transferable skills they offer, such as narrative framing, problem-solving, and iterative thinking. The episode also highlights how everyday experiences and simple activities can yield valuable insights into testing methodologies, underscoring the importance of curiosity, user-centric thinking, and personal growth in professional settings.

Furthermore, the discussion addresses concerns around the misuse of data in the workplace and the need for honesty, humility, and continuous learning. It also touches on the benefits of journaling, the value of patience and adaptability, and the importance of balancing AI with human curiosity in testing and related fields. The episode encourages professionals to reflect on how personal interests and experiences can contribute to their growth and effectiveness in their work.

What If

• What if you applied the iterative, patient mindset from a hobby like knitting or crocheting to your software testing process?

  • Concrete move: Introduce a “testing rhythm” where you break down testing into micro-tasks inspired by gradual, iterative hobby projects (e.g., testing one module per day, similar to finishing one row in a knitting project).
  • Why now: The text highlights how hobbies like crocheting teach patience and incremental progress, which are critical for systematic, bug-free testing.
  • Expected upside: Reduced burnout, more consistent quality checks, and a structured approach to testing that aligns with real-world user scenarios.

• What if you treated data analysis in your product like a game, where the goal is to uncover hidden patterns rather than just “winning”?

  • Concrete move: Set up a “data mystery” challenge for yourself, using historical user behavior logs to predict edge cases or anomalies, similar to how players analyze game stats to improve performance.
  • Why now: The text emphasizes the gaming mindset of accepting failure and experimentation, which aligns with playful data exploration.
  • Expected upside: Identify overlooked issues that analytics dashboards might miss, and foster a curiosity-driven approach to debugging.

• What if you roleplayed as a user with a specific constraint (e.g., accessibility needs, device limitations) during testing, as the episode discussed in the pedestrian crossing analogy?

  • Concrete move: Pick a real user persona (e.g., a visually impaired user, a single-handed user) and simulate their experience while testing your app, documenting how your design adapts or fails.
  • Why now: The text shows how mundane experiences (like waiting at crossings) can inspire user-centric testing, and the user-centric mindset is a recurring theme.
  • Expected upside: Discover critical usability gaps youd otherwise overlook, making your product more inclusive and competitive.

Takeaway

• Incorporate storytelling from hobbies (e.g., pro wrestling, Dungeons & Dragons) into test case creation to improve communication and make complex ideas relatable.
  Example: Frame test scenarios as narratives to highlight edge cases or user journeys in a more engaging way.

• Use user-centric testing principles by focusing on whether a feature works for end-users, not just how it functions technically.
  Example: Validate software by simulating real user behaviors and feedback, especially for accessibility and usability.

• Track personal and professional growth through journaling or progress logs, similar to how hobbies like fitness or music can show incremental improvement.
  Example: Record testing challenges, solutions, and lessons learned weekly to identify patterns in skill development.

• Stay vigilant against data misuse in your work by questioning metrics’ context and avoiding oversimplification (e.g., dont assume stats like “shots taken” fully represent value).
  Example: Cross-verify key performance indicators with qualitative feedback or contextual analysis to avoid biased conclusions.

• Experiment with small, low-risk changes in workflows or tools (e.g., “five-minute coffee calls” before meetings) to identify what improves productivity or collaboration.
  Example: Test a new testing framework or automation tool on a minor feature before full-scale integration to assess feasibility.