Preserving software testing history reveals timeless principles like organizational responsibility for quality, psychological safety, and systems thinking, often overlooked in today’s focus on metrics and speed. The podcast critiques modern practices as rebranded versions of foundational concepts, stressing that true quality requires leadership, accountability, and a culture prioritizing transparency over profit.

The Value of Software Testing

Randy Rice has a video Software Testing podcast - solo shows and interviews. Youtube only.

• https://www.youtube.com/playlist?list=PLGrFXPvIwr2WR6wn-Ngw7_9X_Ec3WO4vK
• https://www.riceconsulting.com/

Episode Details

• Show Notes: https://www.youtube.com/watch?v=51-NSt6_wwc
• Published: 2026-08-28T17:32:47Z
• Duration: 00:25:19
• Author: Rice Consulting Services, Inc.

Overview

The podcast discusses the importance of preserving software testing history, highlighting efforts to archive early conference materials, such as a 400-page notebook from the 1991 QAI International Conference. Special attention is given to foundational figures like Dr. Boris Beizer and his influential paper and book, which shaped early testing practices. The evolution of software quality is examined, noting that the 1980s and 1990s emphasized quality management, risk, and process improvement - principles that have since been overshadowed by technological advancements like cloud computing and AI, despite their continued relevance.

A central theme is the idea that quality is an organizational responsibility, not merely a testing function. Historical practices such as in-process inspections, psychological safety, blameless retrospectives, and systems thinking are revisited as timeless principles that predate modern methodologies like Agile and DevOps. The discussion critiques the current focus on superficial metrics - such as test counts and deployment speed - as a “quality veneer” that often masks deeper cultural failures. It emphasizes that true quality requires leadership commitment, accountability, and a culture where issues can be reported without fear.

The podcast also reflects on how many contemporary practices are rebranded versions of long-established quality concepts from pioneers like Dr. Deming, Juran, and Crosby. Examples from Boeing’s quality failures illustrate the consequences of ignoring these principles, particularly when profit and speed override safety and integrity. The conversation underscores that without a cultural foundation that values transparency, continuous improvement, and systemic thinking, even the most advanced technical tools cannot ensure software quality. The discussion calls for a reintegration of these foundational lessons into modern development practices.

What If

• What if you digitized and open-sourced a lost piece of software testing history that could revive foundational quality principles in modern teams?

  • Move: Identify one obscure but impactful historical paper (e.g., Beizer’s Honey, I Shrank the Risk) or old presentation from your archives, convert it into a well-formatted PDF with annotations, and publish it on a public GitHub repo with a permissive license.
  • Why Now?: Many early testing materials are vanishing; digital preservation is urgent, and developers are increasingly seeking context for today’s broken quality practices.
  • Expected Upside: Establish authority as a bridge between classic quality thinking and modern dev practices; attract inbound interest from educators, senior engineers, and quality advocates - potential for consulting leads or content monetization.

• What if you audited your solo development workflow against Dr. Deming’s 14 Points to systematically eliminate quality debt before it forms?

  • Move: Map each of Deming’s 14 Points to your current solo workflow (e.g., “End dependence on inspection” shift left with pre-commit hooks; “Drive out fear” implement blameless postmortems for bugs in your changelog), then automate at least three high-impact changes using CI/CD scripts or tooling.
  • Why Now?: Solo developers face compounding quality debt due to lack of feedback loops; applying systems thinking now prevents costly rework as products scale.
  • Expected Upside: Reduce bug recurrence by 30 - 50% over 6 months; create reusable templates that can be productized (e.g., “Deming-Compliant DevOps Kit” for indie hackers).

• What if you built a micro-product that exposes the gap between modern Agile theater and real quality culture - using historical principles as a diagnostic tool?

  • Move: Develop a lightweight SaaS quiz (e.g., “How Healthy Is Your Quality Culture?”) based on TQM/Beizer/Deming criteria, scored against 1990s best practices, with personalized reports and actionable fixes.
  • Why Now?: Teams are fatigued by superficial Agile metrics; there’s rising demand for authenticity in engineering culture, especially among tech leads in post-hype startups.
  • Expected Upside: Fast validation via indie hacker communities; potential to convert users into buyers of deeper audits, templates, or workshops - low-code MVP possible in under two weeks.

Takeaway

• Audit and digitize your personal knowledge assets (e.g., old notes, presentations) to preserve insights and identify reusable content for future products or content marketing.
• Shift from in-person conference speaking to webinar-based presentations to reduce travel time and costs while maintaining professional visibility and audience reach.
• Research and seek permission to republish historically significant but inaccessible technical papers in your field to create unique, value-driven content and establish authority.
• Evaluate your current quality metrics (e.g., test pass rates, defect counts) against cultural indicators like psychological safety and blameless communication to identify gaps in real quality practices.
• Reintegrate foundational quality principles (e.g., in-process reviews, shift-left testing, systems thinking) into modern workflows by mapping them to current practices like Agile retrospectives and CI/CD pipelines.