Refactoring improves internal code structure without changing external behavior, while refactorable code provides a safe environment for both improvement and extension.
The development cycle of reading, concluding, and adjusting code can be slowed by negative forces like pressure, ignorance, and fear, leading to decreased quality.
Confidence in reading, understanding, and adjusting code is the positive force that counteracts pressure and fear, enabling a sustainable development pace.
Improve code readability by using expressive names, separating concerns to reduce complexity, and avoiding the 'it works' mindset that accumulates technical debt.
Share domain knowledge and technical context effectively through self-documenting unit tests and detailed, explanatory commit messages.
Adopt test-driven development (TDD) as a design technique and make small, incremental changes with version control checkpoints to adjust code safely.
Investing in refactorable code is not just about developer convenience; it's a financial decision to prevent costly rewrites and build competitive, long-lasting products.
Discussion on how to convince other teams to refactor using tests for safety, when not to refactor, and how to balance refactoring with urgent feature requests.
tree-IT GmbH
Bad Neustadt an der Saale, Germany
24:19Johannes Haux
30:40Olivier Gaudin
41:17Kamila Santos
30:01Tim te Beek
24:38Carola Lilienthal
28:17Hendrik Lösch
43:00Luka Kladaric
35:31Thomas Dohmke
Jobs that call for the skills explored in this talk.
Mein Schiffberater GmbH
Monheim am Rhein, Germany
BVU Beratergruppe Verkehr + Umwelt GmbH
Freiburg im Breisgau, Germany
Thinkbyte Consulting, Inc.
GitHub, Inc.
Orrell, United Kingdom
Reflow
Amsterdam, Netherlands
