How to Do Great Work
summary
Tech lead role at Wayfair starts with a small Android team that has under a year of platform experience, so priority is defining concrete standards: Android-first mindset, readability and maintainability, and feedback is a gift. Practices enforced are SOLID, Kotlin null-safety to avoid nullability, immutability, meaningful naming, don’t repeat yourself, unit tests, and separating UI and data models. The result is clearer code ownership, fewer null crashes, and faster onboarding for junior engineers.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:37What is a manager
- 2:21Barriers to great work
- 3:05Core values for the team
- 5:56SOLID principles
- 7:45Avoiding nullability
- 9:56Promote immutability
- 11:24Meaningful names
- 12:47Avoid duplication
- 13:51Writing unit tests
- 14:54Coding by convenience
- 16:17Summary
related talks
51mBuilding Effective Teams of Competent, Friendly People
34mBeing more than an Android developer
44mRoundtable: How to get into the Android world? Landing your first job and early challenges
27mAfter the Offer: Succeeding as a New SWE
49mBe Like Water: Keeping Up with Android
26mFacing the Anxiety of Being the Only Android Engineer
32mThe Power to Make Things Work — From Android Engineer to Manager and Beyond?
37mHow Android development experience applies outside Android development