Ariya Hidayat (Shape Security) interviewed at Fluent 2014
summary
Argues for static polymorphism: reuse identical function and property names across similar widgets (radio, checkbox, slider) to reduce ambiguity, and prefers descriptive names over double negatives. Recommends two automation steps: a cautious renamer for deprecated identifiers (no brute force) and detectors for boolean traps/double negative patterns; no turnkey suites exist but mix-and-match frameworks let teams build tooling. Success is measured as raised awareness and gradual refactors; uploader: fuentconf.com.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:27Simple things to make your API better
- 1:03Why does nobody read the API documentation
- 1:30What do you do with old code
- 1:45How difficult is it to get developers to adopt
- 2:17How can we automate this process
- 3:05Tools available
- 3:20Success
- 4:02Conclusion
related talks
51mPreventing Security Bugs through Software Design
17mDon't optimize, write optimal by Davit Abgaryan (Arm) | JSConfAM19
27mDesigning Even Larger (JavaScript) Applications
40mDesign Approaches for Security Automation
52mSecure by Design, Revisited - Insights & Pitfalls
28mSecurity Through Design - Making Security Better By Designing for People
30mThe seven righteous fights
38mSecurity Styles