Four Diseases
summary
Examines four recurring anti-patterns with concrete examples and fixes: forms that require postal-code and post-office fields break deliveries (Polish address forms vs post office rules); email validation that uses a brittle regex restricting TLDs to 2–4 chars instead of sending a verification message; and homegrown solutions like roll-your-own CSV/DNS/password hash or storing timestamps as varchar and money as double. Recommends using postal rules or what3words for addressing, verify emails by sending, prefer UUIDs, timestamptz and money types, and reuse battle‑tested libraries.
AI-written summary · about
chapters (5)
- 0:00Introduction and speaker background
- 3:32DDD disease explained
- 15:27Career diarrhea in email validation
- 24:32Not made here syndrome
- 29:41Malicious stream gosling
related talks
52mSecure by Design, Revisited - Insights & Pitfalls
45mBeyond design patterns and principles - writing good OO code
50mCracking the Code to Secure Software
32mRules, Laws, and Gentle Guidelines
58mBuilding antifragile systems using Secure by Design
30mFormal Specification and Taming Other People's Tech
47mExpressing Design in Code: Architecturally-Evident Coding Patterns
42mObject reorientation