~/talk

How to Start Refactoring Someone Else's Code Without Getting Fired in a Month

TalkinUkrainianat JavaScript fwdays'24 conference · on Saturday, 2024-05-25· [frontend-architecture, developer-experience]
links:none on file
slides:none on file

A speaker describes practical strategies for refactoring someone else’s legacy JavaScript code without burning out or getting fired, explaining how they balanced adding new features while incrementally modernizing old code. The talk recounts specific painful experiences, lessons learned about taking time to understand large files, and why legacy code can be an opportunity to improve one’s skills.

AI-written summary · about

  1. 0:00Introduction
  2. 3:55Legacy code analysis
  3. 12:08First week paralysis
  4. 14:39Code analysis via docs
  5. 22:13Refactoring as learning
  6. 24:26Minimal changes
  7. 28:46Step-by-step refactoring
  8. 32:06Task analysis
  9. 36:10Refactoring tips
  10. 37:45Closing remarks
  11. 38:11Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.