PEBCAK
summary
Many failures labeled “technical” are actually human: design and management choices, normalization of deviance (example: Challenger O-ring cascade), and unpatched stacks (Equifax running code from 2005). Concrete fixes include pairing on hard features (saved about a week on a password-reset build), replacing a custom bulk uploader with jQuery file upload plus Sonata form to ship in two days, and adopting a minimum-8-char policy combined with check breached-password list and 2FA to stop most account compromises.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:30About me
- 3:34Technical problem
- 8:28Problem
- 10:05People
- 11:22Problems
- 16:08Reality
- 19:57Developer vs Designer
- 24:03Cooperation
- 27:43Social skills
- 29:44Saying no
- 34:48One point
related talks
43mIf security is hard, you are doing it wrong
47mThreat Modelling Stories From The Trenches
34mNightmare Before Best Practices
46mFire, Brimstone, and Bad Security Decisions
53mTechnical Enshittification: Why Everything is Horrible and How to Fix It
50mFix The Damned Software
26mThe Risky Business of Risk Illiteracy (Sean Juroviesky)
57mBuilding a Modern Security Engineering Organization