What I learned improving complex code in my first year as an engineer
summary
An early-career Android engineer describes tackling legacy product code by migrating incomplete Flux-based Action/Store components toward Clean Architecture, explaining the step-by-step rearchitecture work. The talk covers how the presenter learned unfamiliar architecture and library implementations to make changes, and which design and implementation choices help code remain easy to improve in the future.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:17Legacy project background
- 7:17Catching up with code
- 13:06Redesign strategy
- 17:48Design process and teamwork
- 19:55Implementation and trunk-based dev
- 20:59QA and testing methods
- 23:56Feature flags for releases
- 26:11Project outcomes and lessons
- 28:40Success factors and communication
- 30:28Preventing legacy code
- 34:45Summary
related talks
41mOne year of Clean Architecture: the Good, the Bad and the Bob
47mStep by Step Toward Clean Architecture
28mDesign Improvements for an Existing App Based on the Guide to App Architecture
40mDevelopment Strategies for a 14-Year-Old Android App to Survive a Generational Design Shift
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
32mEffective Android Architecture
31mFrom Zero To A Maintainable, Scalable Architecture On Android
31mPatterns for Safe Refactoring of Android Apps