Impactful Refactors: Refactoring for Readability

on YouTube ↗12m

" summary

Argues for concrete refactors: rename ambiguous instances to post_presenter so type is obvious, annotate methods that return epoch integers as birth_date_as_integer, and prefer explicit long names like agility_cattle_dog_with_a_wheat_allergy when that reduces lookup time. Calls out costly onboarding and slower bug fixes when code is clever or abbreviated, notes painful RubyMine debugging, recommends small well‑named helpers and POODR / The Art of Readable Code as practical resources.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 0:53Save the Unreadable Performant Code
3. 1:12Disclaimer
4. 4:42Abbreviating
5. 7:57Humane Driven Development

" related talks

• 18mImpactful Refactors: Refactoring for ReadabilityKinsey Ann Durham · RubyConf AU 2017
• 45mPanel Discussion RefactoringRails Pacific 2014
• 48mRefactoring from Good to Great - A Live-Coding OdysseyBen Orenstein · RubyConf AU 2013
• 01h 04mRefactoring Is Not Just ClickbaitKevlin Henney · NDC Oslo 2022
• 50mRefactoring Is Not Just ClickbaitKevlin Henney · Build Stuff 2022
• 32mruby best practice patternsRein Henrichs · Lone Star Ruby Conference 2008
• 01h 07mRefactoring Is Not Just ClickbaitKevlin Henney · NDC London 2023
• 20mPre-factoring: Getting it (Closer to) Right the First TimeCoraline Ada Ehmke · RubyConf AU 2015