Главная
Study mode:
on
1
Intro
2
Agenda: 5 important questions
3
Backwards compatibility
4
Three types of compatibility
5
Involuntary API breaks
6
Avoid breaking the API when possible
7
Redundancy can get painful
8
In response to advancing technology
9
Changing the API as a strategy
10
Why we changed the iText design
11
Use semantic versioning
12
A good design to start with is key
13
Use tools to detect breaking changes
14
Avoid being a moving target
15
Ease the pain
16
Avoid back-porting
17
Have a clear EOL strategy
18
It's the fault of Marketing
19
It's the fault of Sales
20
Making development future-proof
21
Big bang release or early release?
Description:
Save Big on Coursera Plus. 7,000+ courses at $160 off. Limited Time Only! Grab it Explore the complexities of API changes in this thought-provoking conference talk aimed at SDK and software library developers. Delve into the arguments for and against modifying APIs, weighing short-term pain against long-term benefits. Learn strategies for introducing new APIs, maintaining user loyalty, and balancing backwards compatibility with technological advancement. Discover the importance of semantic versioning, clear end-of-life strategies, and tools for detecting breaking changes. Gain insights on creating future-proof designs, managing redundancy, and deciding between big bang and early releases. Examine real-world examples from iText Software's experience and understand the impact of marketing and sales on API development decisions.

Oops, I Broke My API

Devoxx
Add to list