FOMO - How an Android dev cut through the noise and build proactive learning habits
summary
Claims that constant churn forces developers to manage ~20–25 libraries per app and test across ~12,000 device SKUs, cites concrete signals: Android 14 migrations, Kotlin 1.9/K2, KMM, Compose for TV and Jetpack Glance in alpha, and an example library update to compose-bom 1.0.6. Advises learning from experience (docs, GitHub, YouTube), using Retrofit as a real example, prioritizing user needs, avoiding overengineering, and “learn only when you need it” to cut FOMO/FOS.
AI-written summary · about
chapters (10)
- 0:00Introduction to FOMO in Android
- 1:31Google IO highlights and excitement
- 4:44Android engineers life cycle and library updates
- 10:23Fear of social media in tech
- 14:38Where to learn: sources and best practices
- 16:46Coping with FOMO and prioritizing learning
- 19:15Debunking Android myths and challenges
- 22:07Native vs hybrid and Compose vs XML debates
- 23:53Negative impacts of FOMO on productivity
- 24:14Closing remarks and shameless plug
related talks
49mBe Like Water: Keeping Up with Android
34mBeing more than an Android developer
26mKeynote: Being more than an Android Developer
26mFacing the Anxiety of Being the Only Android Engineer
34mStaying Relevant
45mFor Beginners and Career Changers: Android App Development Today and Key Points in 40 Minutes
37mPersonal Projects as a Laboratory: Four Freedoms an Android Engineer Gains
30mWhat I Learned in Two Years as an Android Engineer