The hottest Quality Assurance Substack posts right now

And their main takeaways
Category
Top Technology Topics

Meet Bug, the QUALITY BOSS Mascot

QUALITY BOSS • 0 implied HN points • 06 Nov 23
🕹 Technology Quality Assurance
  1. The mascot is a firefly named Bug, symbolizing the journey towards achieving high quality. Bug is meant to guide and inspire everyone to reach excellence.
  2. The term 'bug' usually refers to problems in software, but here it's reimagined as a positive force for growth. Each bug is seen as a chance to improve and learn.
  3. Bug not only represents quality but also highlights unique experiences in the tech industry, especially for women. This fosters a community focused on exploration and learning.

On Managing Risk in Software Projects

Anant’s Newsletter • 0 implied HN points • 19 Jun 24
🕹 Technology Quality Assurance
  1. Understand user needs clearly to avoid creating features that don't solve problems; involve users early in testing to catch issues.
  2. Ensure all teams understand their roles and dependencies to prevent surprises; clarify API contracts and dependencies early on.
  3. Plan integration and testing carefully; start integrating early and create detailed testing plans to ensure everything works before launch.

Les mocassins de quelqu'un d'autre

Squirrel Squadron Substack • 0 implied HN points • 26 Jan 26
🕹 Technology Quality Assurance
  1. Automated status messages can be contradictory, for example saying a device is repaired while warning the keyboard or screen may not work, which confuses customers.
  2. If engineers or technicians don’t use and test the system themselves, they won’t notice silly or harmful messages that slip through.
  3. This gap between automation and human oversight can cost time, trust, and business; either update the system or make sure people regularly use and correct it.

🐿️ Danger of Death - The Insanely Profitable Tech Newsletter

Squirrel Squadron Substack • 0 implied HN points • 09 Feb 26
🕹 Technology Quality Assurance
  1. When software can cause physical harm, use multiple layers of automated and human checks and avoid risky release practices.
  2. Many teams apply safety-critical processes to low-risk products and end up polishing for months, which wastes time and yields diminishing returns.
  3. Focus your engineers on finding and building what users actually need and will pay for, rather than protecting against unlikely catastrophic scenarios.

🐿️ Tracer Bullets - The Insanely Profitable Tech Newsletter

Squirrel Squadron Substack • 0 implied HN points • 06 Feb 26
🕹 Technology Quality Assurance
  1. Treat mistakes like tracer bullets: run cheap, fast experiments that will often be wrong so you get immediate feedback and learn quickly.
  2. Don’t stop at technical fixes — use failures to change culture and processes so you root out over-optimism, whitewashing, and the normalization of bad practices.
  3. Build disciplined rapid-learning loops: ask why repeatedly, do frequent post-mortems, and update norms so teams converge on the right results and make mistakes harder to repeat.
Get a weekly roundup of the best Substack posts, by hacker news affinity: