"Fail.lure"
summary
Claim: deliberately make systems fail to produce cleaner code, using a simple three-part framework that groups ignore / lure / allure into actionable steps. It lists nine actionable tips (three per pillar): contain / intimate / record for robustness; diligently check / curiously test / continually revise to seek bugs; be beautiful inside / attractive outside / entice customer to visualize the perfect. No specific tools or demos are shown, the value is practical rules of thumb rather than measured results.
AI-written summary · about
related talks
25mThe Pursuit of Failure
04mHow to fail (Lightning Talk)
37mFailing Well: A Practical Guide to Growth for Technical Writers
31mFail Early, Fail Often, Fail Well
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
39mThe Three Laws of Test Driven Development are Useful
44mEnhancing your Testing Skills with "Mindset Tools"
24mHow to solve intermittent issues, aka Random Failures