Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Git Driven Refactoring by Ashley Ellis Pierce Often we know that our code needs refactoring, but we have no idea where to start. Maybe we studied some common code smells and learned about the things that we should be avoiding, but memorizing the rules doesn’t automatically lead to fixing all problems. In this talk, we explore how you can use Git to recognize and address violations to each of the SOLID principles. Using diffs, commit history and pull requests you can learn to recognize patterns in code that point to problems. These same tools can help you correct those issues and write more maintainable code.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In her talk "Git Driven Refactoring" at RubyConf 2017, Ashley Ellis Pierce, an application engineer at GitHub, discusses the challenges of identifying and addressing code that needs refactoring. Refactoring involves changing the structure of code without altering its behavior, yet many developers struggle to pinpoint the problems within their codebases. To aid in this process, Pierce emphasizes employing Git as a tool to analyze code against the SOLID principles, a set of five design principles aimed at making software more flexible and maintainable. ### Key Points Discussed: - **Understanding Refactoring:** Refactoring is essential for cleaning up messy code, and while developers often recognize that refactoring is needed, they may struggle to identify where to start. - **SOLID Principles:** Pierce outlines the SOLID principles: - **Single Responsibility Principle**: A class should have only one reason to change. - **Open-Closed Principle**: A class should be open for extension but closed for modification. - **Liskov Substitution Principle**: Subclasses must be substitutable for their parent classes. - **Interface Segregation Principle**: No client should depend on methods it does not use. - **Dependency Inversion Principle**: Depend on abstractions, not concretions. - **Using Git for Refactoring:** - Git logs reveal the history of changes in classes, helping identify violations of SOLID principles. For example, grouping commit histories can highlight whether classes are handling multiple responsibilities. - The presence of modifications (red in diffs) when adding new features signals potential violations of the Open-Closed principle. - **Automation and Tools:** Leveraging GitHub tools, such as automatic checks for code quality, helps ensure adherence to design principles without solely relying on manual code reviews. Pierce encourages creating custom bots that can help detect design principle violations during pull request reviews. ### Examples and Illustrations: - Pierce shared personal experiences, recalling her time at Thoughtbot, where she encountered challenges in recognizing design problems until she utilized Git to explore the history and context of changes. - She discussed how looking at commit histories allowed her to group changes thematically, leading to more effective refactoring decisions. ### Conclusion and Takeaways: - Developers should actively use Git not just for version control but as a lens to identify design principle violations. - Clear and consistent commit messages, along with proactive automation practices, can facilitate easier and more effective refactoring. - By applying the SOLID principles, developers can produce more maintainable and adaptable code, minimizing future technical debt. Ultimately, Pierce’s talk inspires developers to view Git as a critical ally in their refactoring efforts, equipping them with practical strategies to create better codebases.
Suggest modifications
Cancel
