Hype Driven Development: How I learned to stop worrying and love the failures
summary
Claims that chasing hype is OK if confined to a sandbox and risk-managed; builds a conference-listing app using GitHub content + GraphQL, Firebase Functions (TypeScript) then Kotlin multiplatform for shared models, Firestore and JetBrains Compose (desktop), hits failures: dirty YAML, API rate limits, missing Firebase JS artifacts, Kotlin/JS dynamics, flaky CI, eventual migration to Google Cloud Functions (Java) that works better. Recommends feasibility studies, disposable code, opt-in annotations and open playground repo experiments.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 1:10Decision-making in development
- 4:22Hype and community influence
- 8:33Risks of immature software
- 10:58Risk management techniques
- 13:08Solutions looking for problems
- 15:59Weighing risks and benefits
- 17:24Hype-driven development in practice
- 19:28Playground project demo setup
- 23:12GitHub API challenges and GraphQL
- 24:55Kotlin multiplatform experiment
- 27:43Failure and learning from mistakes
- 29:49Safe environment for experimentation
- 31:32Balancing work and personal projects
- 33:17Conclusion and advice
related talks
44mHype Driven Development
34mNavigating the hype-driven frontend development world without going insane
30mNavigating the hype-driven world of frontend development without going crazy - 'Kitze' Ristovski
34mNavigating the Hype-Driven Frontend Development World Without Going Insane
25mBuild Failed Startups—Not Side Projects
41mCreating A Better Developer Experience By Avoiding Legacy Code
41mIgnite Sessions
36mIterative Mobile Development