Impactful Refactors: Refactoring for Readability
summary
Argues that refactoring for readability beats micro-optimizations and shows concrete wins: a 300+ line Backbone view gets split into small POJOs, a filter processor Factory and per-filter processor classes, a shared base class extracted, Jasmine tests added, and a bug fixed; the refactor deletes many lines and comments and completes in a day. Claims readable code reduces onboarding time, lowers cognitive load, supports inclusion, and makes future changes easier.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:35REFACTORING
- 0:45DESIGN PATTERN
- 0:59MAKING CODE READABLE
- 2:31PREVIOUS VERSION OF THIS TALK...
- 3:42TWO EXAMPLES
- 4:34BABY STEPS...
- 5:36WRITE GOOD TEST DESCRIPTIONS
- 6:36WRITE FANCY CODE IN SIDE PROJECTS
- 7:57DISCLAIMER: JAVASCRIPT AHEAD
- 10:57TRULY READABLE CODE MEANS GOOD DESIGN
- 11:52CODE REVIEWS
- 12:23ENGINEERING CULTURE
- 12:39SWITCHING CONTEXTS
- 13:19BUG FIXING
- 13:37BEST PRACTICES
- 14:00REMOTE
- 14:21ONBOARDING
- 14:35We are humans, developing software with humans, to benefit humans...
- 14:57DIFFERENT BACKGROUNDS
- 16:56RUBY COMMUNITY
- 17:35ALWAYS BE QUESTIONING YOUR CODE
related talks
12mImpactful Refactors: Refactoring for Readability
01h 04mRefactoring Is Not Just Clickbait
50mRefactoring Is Not Just Clickbait
48mRefactoring from Good to Great - A Live-Coding Odyssey
45mPanel Discussion Refactoring
55mHow To Approach Refactoring
01h 07mRefactoring Is Not Just Clickbait
37mRefactoring: A developer's guide to writing well