Trends & anti-patterns; navigating the digital landscape for future survival
summary
Argues that survival depends on treating APIs as products with self-service and fast time to market and prioritizing UX over bespoke tech choices; recommends hybrid architecture, accepts native vs cross‑platform tradeoffs, and warns that modernization is not transformation. Rejects vanity metrics — don't count raw API transactions — and advises not to monetize developer access early — charge developers zero — instead track NPS, active developer/partner orgs and completed business transactions. Emphasizes data-as-currency, platform + ML strategies, and layered separation of duty for API security.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:05What is at stake
- 2:22Trends stop scaring everybody
- 3:39Good architecture
- 5:40APIs
- 8:10Legacy languages
- 9:06Why companies fail
- 10:24How to measure success
- 12:03Misleading modernization for transformation
- 13:24Focusing on the wrong variable
- 14:58Philosophy
- 15:59Predict the future
- 19:22Data currency
- 19:48Platform vs ML
- 21:10Giraffe
- 22:08Questions
- 23:08Metrics
related talks
27mAPI Economy and Ecosystem
15mThe global trend of platformication
28mAPI Productisation - shift RIGHT to Better Product Resilience
26mMastering API Strategies for Digital Transformation
40mUnlocking the secret to success in the API Economy
33mDesigning Sustainable APIs
16mBuilding Future-Proof API Platforms
54mAPI team characteristics and best practices