Learn together. Not the same
summary
A Deliveroo Android team spends 1.5 years converting three apps from Java to 100% Kotlin, using GitHub automation (an auto-assign script) and requiring two reviewers to spread knowledge. Conversions stay in separate commits, code reviews become learning sessions with explanatory comments, and a Kotlin meetup ("Kotlin hour") surfaces patterns like using default interface implementations and adopting Spotless for style. The process introduces merge conflicts and some bugs, but overall reviews speed up shipping and improve readability.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:13AMERICAN EXPRESS
- 3:29Collaboration through code reviews
- 5:54One goal: Sharing knowledge
- 9:10Assume that anyone you're teaching has no knowledge, but infinite intelligence.
- 9:45Code reviews are for more than just correctness
- 10:56Create forums for discussion
- 13:44Leveraging a common context
- 14:41Fight for your right to learn
- 15:10Add value to yourself And your company
- 16:42Share knowledge
- 18:53No gateway to shipping
- 20:25Be mindful about commits
- 20:53Ship faster
- 21:54Converting a project means rewriting it
- 22:36Communication is crucial
- 23:15Use all the things
- 24:21Split up pull requests
- 25:20Get feedback early
- 26:04Get feedback in advance
- 26:53What does this mean for you?
- 27:20Making a success of Kotlin hour
- 28:03Invite and advertise
- 28:49Use the hive mind
- 29:35Share what you learn
- 30:14Create forums for learning and up-skilling your team
- 30:31If it doesn't exist Make it
- 31:02Learning has no definition of "done"
related talks
31mGetting to 100% Kotlin: A Practical Guide
31mKotlin: A Followup
31mA Kotlin Journey
26mKeynote: Being more than an Android Developer
49mBe Like Water: Keeping Up with Android
38mThe Highway That Trains Androiders and Where We Landed After Real-World Battles
15mKotlin Multiplatform Contest Winners
36mAndroid to Full-Stack: A Devs Journey to the Great Unknown