Christina Thalayasingam: Great Products Come from Engineering Teams...
summary
Claims that quality is a team responsibility backed by concrete changes: move tests into the development repo, shift effort from flaky GUI suites to more unit and integration/API tests, run synthetic monitoring every 15 minutes that pages on failures (caught a CrowdStrike-like outage), run cross‑discipline bug bashes, use feature‑flagged releases to engineers/friends‑and‑family for in‑production validation, and use tools like Selenium (25‑year mark), Heap, AppQ, New Relic/Dynatrace and GitHub Copilot to speed testing and feedback.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:31Bug and debug origins
- 3:40Quality everyone’s job
- 5:49Testing evolution to collaboration
- 7:56Waterfall’s impact on quality
- 9:45Breaking silos at Northwest Mutual
- 12:32Manual to automated testing
- 14:38Quality mindset across teams
- 16:01Bug bashes and release testing
- 17:06Synthetic monitoring
- 19:19Preventive quality approaches
- 21:28Data-driven decisions
- 21:49Empathy for end-user needs
- 24:41Feature flags for safe testing
- 27:11User onboarding feedback
- 30:40Quality beyond testing roles
- 32:04Key takeaways
- 35:18Closing remarks and call for questions
related talks
55mQuality Engineering Evolution: What Lies Ahead in
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook
17mStaying Ahead: The Future of QA Leadership
49mChanging Testing Culture in a Ginormous Company
28mScaling Tech Work While Maintaining Quality - Hint - Community Is The Answer
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
31mAssembling Excellence: Crafting a Quality Assurance Team from the Ground Up
33mSoftware development practices for companies that want to make an impact