Refactoring, Extraction, and Naming

As developers, naming is our most powerful tool to make our code understandable. It's an essential part of refactoring. Learning what to pull out, and what to name it, makes our code more maintainable. In this episode, you'll learn how to apply essential refactorings like Extract Method and powerful techniques to tell at a glance whether your code is doing too much.

This is a companion discussion topic for the original entry at

I think this is a really important topic. Refactoring and extraction are often talked about, but it is rare to see a good example of how to do it. Thanks for this. I think that was the most productive 20 min of my week.

One of the reasons why I like naming things (besides informing future me and other developers as to why I’m doing something) is that I can create stubs for these methods while writing tests.