I love it when I learn something in a casual conversation and can publish it as a podcast episode as a side-effect. This @case_podcast on functional architecture with @sperbsen was one of those occasions case-podcast.org/31-mike-spe…
Neugierige Frage: Denkt man eigentlich nach, bevor man so etwas schreibt, und entscheidet dann, dass einem die Konsequenzen egal sind? Oder haut man da mal eben raus, was einem durch den Kopf geht, egal wie dämlich es ist?
Because they feel this will finally give common structure to their IT; because they believe it will make them faster; because analysts or vendors told them they need to do it
If you provide an API as a product, e.g. as a SaaS provider, you’ll consider the developers your end users. If that’s not the case, my point is that you’re right: Your end users don’t care about APIs, so you shouldn’t put them at the center
I agree that once you’re sure you know what service you want to build (including that you even want to build it in the first place), doing it contract-first is a good idea