In recent years, “API first” has been used very excessively. Many people believe that this is the only truth in the design of APIs, “Only through … first we achieve a faster time-to-market”, “the provided APIs become better” and so on. The principle of code first, lived for many years, should now no longer be good enough.
That’s the theory! But no one has spoken to teams that deliver “good” APIs even without API first. But whether these APIs also meet the possibly new guidelines is another matter.
In his talk, Daniel wants to show ways in which teams can create APIs without API first dictates, with the appropriate speed and quality, which also meet the requirements of the entire organisation.