A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
https://www.youtube.com/watch?v=hUyuuXLKi2A
I think it's a good introduction on building APIs, although in parts it's very
technical (they try to sell their tool...).
The interesting parts in the first segment are around how upfronting an API
design can enable multiple teams to work in parallel. >
It provides the contract between the teams, and the individual teams will use
mocking tools to ensure that their implementation follows the API specification.
The negative aspect there IMHO is that it postpones the integration efforts and
before work can start the API really has to be very well thought out to its full
extend so that teams can depend on the API not changing during development.
Another good aspect is how they put an emphasis on starting from the business
use case. This is really helpful to understand why an API is getting built.
Start with a Mission, Personas and User Stories!