The seven righteous fights
summary
Seven concrete engineering habits: hire a localization expert for a week and never hard‑code UI strings; plan for encryption, SSL between services, data deletion and don't roll your own auth; design APIs as if they will be public; publish developer and user docs and prioritize release notes matter; test affordance by stepping down to user permissions and watching microtext and error messages; validate with actual users doing real tasks (firefighters, sysadmins); run accessibility checks (screen readers, color contrast, mouse‑free flows).
AI-written summary · about
chapters (10)
- 0:00Start
- 1:29Definition of a Technical Writer
- 5:44The Seven Righteous Fights
- 7:15Don't hard code interface elements
- 9:26Security is neither cheap nor easy
- 9:41Encryption
- 13:47Documentation is not state secrets
- 16:02Secretive build engineers
- 20:37If you can't hire an expert
- 27:13Pair programming for best practices
related talks
36mThe 7 Battles of Software Architecture: How to Protect Your Project!
01h 03mSeven Security Sins: the seven biggest Security Problems of agile Projects
29mDefence in depth
28mSecurity Through Design - Making Security Better By Designing for People
01h 02mLock That Sh*t Down! Auth Security Patterns for Apps, APIs, and Infra
26mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
57mThe Developer's Field Guide to Software Security
01h 03mWhy Don't Users Do What They are Supposed to Do? A look at users and security