#127 - How the Flocking Rules Can Help You Refactor Your Code

In this new podcast episode we are excited to have Chris May back to delve deeper into the intricacies of refactoring. We talk about the significance of the Flocking Rules, a set of guidelines derived from "99 Bottles of OOP" by Sandi Metz and Katrina Owen. These rules provide developers with a systematic approach to refine their code by focusing on recognizing similarities, identifying minimal differences, and making straightforward changes. We also talk about the importance of taking small, incremental steps in refactoring, ensuring code health while mitigating the risks of accumulating technical debt. We reference some useful resources along the way. Last but not least, we talk about the book Chris recommended last time (episode 119): Building a Second Brain, and how it helps him stay organized and be more productive. Chapters: 00:00 Intro 00:20 Chris May and refactoring topic intro 01:10 25% ratio refactoring 02:14 Flocking rules (99 bottles of OOP) 05:30 Continuously managing technical debt / Slack channel 06:14 Why the flocking rules are great + 99 bottles backstory 08:30 Code towards a design pattern vs go with the flow 09:57 First draft - we often don't know the design upfront 10:37 Python Design Patterns resource by Brandon Rhodes 12:32 Take the smallest possible steps when refactoring 13:57 Advantages of taking small steps 15:18 'Building a second brain' book and how it works for you 19:10 Obsidian as favorite note taking tool 20:02 More inspiration and stories from the book 22:16 Check out Refactoring Toolkit + how to reach out + thanks 23:44 Outro Resources: - 99 bottles of OOP book - Python Design Patterns - Building a second brain - Chris' Refactoring Toolkit - Previous episode with Chris Reach out to Chris: - Website - Mastodon - Twitter - LinkedIn - Pybites Community (we have a dedicated #refactoring channel 😍)