Creating A Better Developer Experience By Avoiding Legacy Code

on YouTube ↗41m

" summary

Argues that legacy pain comes from untestable code and tightly coupled third party tools and offers concrete fixes: inject dependencies instead of calling Firebase or Crashlytics statics, create an error reporter interface to wrap vendors so swapping to Sentry is a one line change, document workarounds with links (example ViewPager code replaced later by ViewPager2), and deprecate globals while incrementally replacing them so tests and confident refactors become practical.

AI-written summary · about

" chapters (9)

1. 0:00Avoiding legacy code
2. 1:01Legacy code defined
3. 4:53Preventing legacy code
4. 7:20Causes: lack of tests
5. 9:27Untestable code issues
6. 13:40Wrapping dependencies
7. 20:59Documentation to prevent unmaintainable code
8. 31:10Key strategies recap
9. 32:34Q&A

" related talks

• 42mWorking Effectively with (Android) Legacy CodeTy Smith, Chuck Greb, Mohit Sarveiya, Joaquim Verges · droidcon San Francisco 2018
• 39mThe End of Legacy CodeDaniel Huss · RailsConf 2023
• 37mWorking Effectively with Android Legacy CodeChuck Greb · DevFest Ukraine 2018
• 01h 01mGuide to Destroying Codebases the Demise of Clever CodeGabor Varadi · Android Worldwide 2022
• 43mBuilding for DevelopersTy Smith · droidcon Italy 2019
• 35mQuickly and Safely Refactoring Legacy CodeJason Swett · SolidusConf 2019
• 33mGuide for lazy developerMaria Neumayer · Droidcon Italy 2018
• 22mHow to write better legacy code: A developer's wishlistBhaman Nikkahan · NDC Melbourne 2022