Explore the principles of effective API design in this keynote address from EuroPython 2011. Delve into the concept of APIs, their importance in software development, and common anti-patterns to avoid. Learn about various types of APIs, the dangers of having no API or poorly designed ones, and strategies for creating robust interfaces. Examine real-world examples of API design pitfalls, including issues with transition planning, fear of commitment, and inconsistency. Gain insights into the human aspects of decision-making in API design, programming language support, standard protocol adherence, and performance considerations. Discover how to create APIs that enhance debugging, documentation, and overall software quality.
Overview
Syllabus
Intro
When you do software
What's an API
What's an Anti-pattern
API Design Antipatterns
More kinds of APIDAS
The very worst APIDA
Why "no API" is bad
What to do instead
The accidental API
Why "no design" is bad API
Wtdi: Think
Wtdi: Forget
A worst-case bad API...
Too many cooks APIS
API Transition: must plan!
Fear of commitment
The "Let's do both!" APIDA
gmpy as a bad example
To decide is human
Inconsistency APIDAS
Why inconsistency?
Prog.language support
Standard-protocol support
Debugging errors, docs
Performance issues
Taught by
EuroPython Conference
