Shifting Out: A Crucial Dimension To Left And Right
summary
Argues for a third axis beyond left/right called Shift-Out that demands zooming to program-level causes, signals, and responses; describes using eBay’s tell us what you think verbatim stream, tagging thousands of reports, and training a small LLM called John bot that automates those tags — it starts noisy but improves over months and reduces manual triage; contrasts that with an NTSB-style Alaska Airlines door-plug failure and a browser-extension test tool whose concrete bugs reveal where automation can and cannot find issues.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:14Welcome to Portland
- 5:01Shift left and right in DevOps
- 7:13Procrastination in shifting right
- 10:04Alaska Airlines Flight 1282 incident
- 12:34Shifting out concept
- 13:19Shifting in: details and processes
- 15:25Zooming out: Earth perspective
- 16:53Shifting out applied to Alaska Airlines
- 21:07Customer feedback at eBay
- 24:41Shifting left, right, in, out in quality
- 25:46Testing mindset with AI threats
- 31:03Browser extension testing case
- 35:17AI and critical testing insights
- 36:42Value of shifting way out
- 37:46Quality advocacy
- 38:49Benefits for testers and managers
- 41:13Q&A: Hardware vs software quality
- 44:58Q&A: Zooming in and out metaphor
- 49:16Q&A: Shifting out in HVAC IoT
- 51:24Q&A: Program manager role
- 53:37Q&A: Building the John bot
related talks
52mShift Left or Squish Right - Testing in a Shifting World
40mEmbracing Shift-Left Testing
47mMaximizing Outcome: Approaching Product Development with Both Shift-Left and Shift-Right Practices
20mShift-left testing : Building reliable Data Pipelines
18mShift Left
48mOwning Our Narrative
01h 28mShift-Left Testing
30mThe Feedback Loop from Hell