Comedy Talk – Better Android Development (BAD)
summary
A satirical playbook that actually names tools and decisions: recommends stuffing repositories, services and UI into a single-activity-with-everything file, bans data binding in favor of view binding or Compose, and peddles a physical “bad box” and shrine. It patents “Death Star architecture” with an exhaustVent.kt backdoor and bigGun.kt to resist process death. Claims switching to shift right manual testing cut dev cycle time ~50% and dropped failing unit tests to near zero; RxJava, coroutines, WebView-offload (DUMP) and notification-first (PAIN) are mocked and inspected.
AI-written summary · about
chapters (10)
- 0:00Introduction and welcome
- 1:09Introducing the BAD approach
- 4:22Bad workspace setup
- 7:33Bad activities and lifecycle
- 11:31Bad UI development choices
- 14:46Death Star architecture
- 19:23Bad async programming
- 22:08Manual testing only
- 28:59Evil spirits in Android
- 31:50Summary and Q&A
related talks
34mKeynote: Comedy Talk - Better Android Development (BAD)
34mFunctional Android
42mIngredients for a healthy codebase (en)
54m10X Android Development
42mWorking Effectively with (Android) Legacy Code
40mEffective TDD on Android with Kotlin
29mDon't reinvent the wheel, use libraries: Modern Android Stack
40mApp Development - Pragmatic Best Practices