KotlinCraft: Building Resilient, Testable, and Scalable Applications in the Modern Era
summary
Gives concrete practices and outcomes: using sealed interfaces for explicit state and null safety gates to filter bad input, switching to Kotlin cuts crashes by about 30%, and parent/child coroutine structure contains failures without bringing down the system. Recommends offline‑first local DB sync, a testing pyramid (fast unit tests, targeted integration, minimal UI), and measuring lead time, recovery time, and team autonomy to speed delivery. Warns that slow CI and flaky UI tests kill velocity and that decoupled domains ease future Gemini/AI integration.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:03Talk overview
- 2:27Feature pressure risks
- 5:13Staff engineering role
- 7:00Syntax as architecture
- 9:09Sealed interfaces & null safety
- 11:18Resilience philosophy
- 13:46Concurrency & fault isolation
- 16:16Offline-first design
- 17:20Resilience building blocks
- 18:43Testability as design
- 20:30Architecture correctness
- 21:57Unit tests foundation
- 23:19Integration & UI testing
- 25:26Testing speed impact
- 26:49Coverage vs efficiency
- 28:17Testability summary
- 28:58Conway's Law & teams
- 30:45Build speed optimization
- 32:12Measuring what matters
- 34:01Sustainable velocity
- 35:48Architecture for AI
related talks
31mA Kotlin Journey
28mSafe Kotlin
47mFew Tools: How To Write And Understand! Coroutines Tests
43mEffective Unit testing with Kotlin
44mKotlin is for hipsters
39mHow to Kotlin - from the lead Kotlin language designer
39mKotlin, Practically Speaking
52mKotlin Backend Development 6 Yrs Recap. The Good, the Bad and the Ugly