OG Refactoring (Observing Gamma): Patterns to Refactor Towards

Track: Tools and techniques

Abstract

Erich Gamma, et al's Design Patterns: Elements of Reusable Object-Oriented Software came out in 1994. Martin Fowler’s Refactoring: Improving the Design of Existing Code was first published in 1999. Joshua Kerievsky's Refactoring to Patterns in 2004.

What have we learned since then about refactoring? What do we, as professional software developers, need to know before deciding to do a refactor on a legacy codebase?

The audience for this session are software developers and the people that interface with them (product owners, scrum masters, development managers) who need to know the value of this important and often neglected technical practice.

At the end of the session, the attendee will be able to identify hidden patterns in their code bases, plan a refactor effort on legacy codebases, write their own refactorings, and recognize accidental code complexity in large codebases.

Aaron McClennen

A 27 year java veteran. I wrote my first java program in java 1.0 when AWT on the mac and unix were different. Since that time I have written uncounted lines of java code, and rewritten most of them. When I first read Fowlers Refactoring my life changed for the better as I realized there was a safe way to fix code that no longer suited.

M. Jeff Wilson

M. Jeff Wilson is an avid software developer, published author, certified scrum master and SAFe Program Consultant, and lifelong learner. He has worked with teams in the telecommunications, insurance, traffic engineering, retail, and other industries to develop and deliver solutions and improve processes. Jeff has been coding since 1981, starting with punch cards and FORTRAN at Georgia Tech, and BASIC on a friend’s Apple IIe. Jeff enjoys gaming, running, music, homebrewing, and, yes, coding in his spare time.