“The Power of No”
summary
A $400 million company fails in under an hour after old code remains, one production server isn’t updated, and post-release monitoring is missing, so the concrete claim is: check removals, updates and monitoring. Examples include a customer proxy breaking integration, apps crashing when expected data or permissions are not present, flaky networks causing unfinished multi‑step tasks, and automation that misses cases vendors do not disclose; prioritize what to skip and what to test.
AI-written summary · about
related talks
15mWhy I Prefer Good Testing Over Excellent Testing
09mWhen I broke production, and it almost broke me
46mFlaky, Fragile, and Forgotten: The Fall of a Test Automation Project
32mStop Automating, Start Investigating: Slow Down 2 Speed Up
39mConfessions of a Systems Engineer: Learning from My 20+ Years of Failure
29mWhat could possibly go wrong?
24mThe more we test, the worse?
29mEmbracing Failures to Avoid Meltdown