Refactoring improves software design and makes code easier to understand without changing its external behavior.
Refactoring can be done preparatorily, for understanding, to remove dead code, as a long-term project, or ideally during code reviews.
While beneficial, refactoring can increase delivery time, cause merge conflicts, and require tests to be rewritten.
Code smells like duplication, long methods, confusing names, and outdated comments indicate underlying problems that refactoring can fix.
Improve readability by grouping code into a new function or simplifying complex expressions by storing them in a descriptive variable.
Control data access by making variables private with getters/setters and simplify method signatures by grouping related parameters into a single object.
Decompose a method that performs multiple distinct tasks into separate, more focused methods to improve clarity and maintainability.
Refactor large classes by using extract class, remove unnecessary intermediaries with remove middle man, and move functions to more appropriate classes.
Improve the codebase by removing unused code, changing value objects to references for shared identity, and decomposing complex conditional logic.
Replace simple constructors with flexible factory methods, move common methods to a superclass with pull up method, and simplify hierarchies by collapsing unnecessary layers.
Refactoring techniques should be combined and used alongside principles like SOLID to solve specific problems and improve overall code quality.
The speaker answers questions on how to prioritize refactoring tasks, the benefits of the split phase technique, and when to use change value to reference.
48:42Dominik Przybysz
41:17Syed M Shaaf
54:58Gil Zilberfeld
50:10Aicha Laafia
41:37Dan Lebrero
45:39Amanda Martin
56:49Jens Happe
45:30Michael Inden
Jobs that call for the skills explored in this talk.
wunschlösung GmbH
Jena, Germany
wunschlösung GmbH
Jena, Germany
Saby New Compy
Bielefeld, Germany