10 reasons why we like certain APIs and other APIs annoy us
summary
Examines why some APIs are loved while others frustrate developers by comparing usability patterns and anti-patterns across real-world examples such as jQuery (good) and java.util.Calendar (bad). Identifies ten concrete reasons that make APIs pleasant or annoying, illustrating each reason with successful and unsuccessful API designs.
AI-written summary · about
chapters (25)
- 0:00Intro
- 4:39User Experience
- 7:06Usability
- 10:41Naming - Ubiquitous Language
- 11:19Naming - Don't do this
- 12:22Naming - Tradeoffs
- 12:50Naming - Consistency
- 16:11Simplicity - Technical View
- 16:33Simplicity - Manager Version
- 17:05Simplicity - Spiritual View
- 18:13Simplicity - See also convenience
- 19:09Simplicity - How to be simple
- 20:22Do One Thing
- 20:44Types - Typesafety
- 22:13Types - Recognise the outline of this talk?
- 27:54Discoverability - JPA good part
- 28:59Discoverability - Bad examples (IMO)
- 32:21Error Handling
- 37:42Convenience - Dogfooding
- 39:44Convenience - In the Java language
- 40:03Compatibility - Don't be like Python
- 40:48Compatibility - The other extreme
- 41:16Compatibility - Be pragmatic
- 41:33Compatibility - A Collection of Tricks
- 42:16Documentation
related talks
52m10 Reasons Why we Love Some APIs and Why we Hate Some Others
35mThe Good, The Bad and The API
18mBuild a terrible API for people you hate
01h 06mGood API design
52mTop 10 Rest API Design Pitfalls
01h 05mAPI design - tips from practice
14mDesigning APIs That Humans Love
01h 01mAPI Design – How to Do It Better (and How Not To)