Much of refactoring is devoted to correctly composing methods. In most cases, excessively long methods are the root of all evil. The vagaries of code inside these methods conceal the …

You can either refactor the tests themselves or write an entirely new set of higher-level tests. A great way to avoid this kind of a situation is to write BDD-style tests.

Refactoring helps you understand other people’s code. If you have to deal with someone else’s dirty code, try to refactor it first. Clean code is much easier to grasp. You will improve it not …

Refactoring is the controllable process of systematically improving your code without writing new functionality. The goal of refactoring is to pay off technical debt. The mantra of refactoring is …

Clean code The main purpose of refactoring is to fight technical debt. It transforms a mess into clean code and simple design. Nice! But what’s clean code, anyway? Here are some of its …

When to refactor How to refactor Catalog Code Smells Bloaters Long Method Large Class Primitive Obsession Long Parameter List Data Clumps Object-Orientation Abusers Switch …

Dive Into Refactoring teaches you how to properly deal with legacy code, how to identify ugly code and how to clean it safely. The course covers 21 smells of bad code and 66 refactoring …

Full list of refactoring techniques and code smells. It's better to understand what's wrong with the code before trying to improve it. Once problem is determined, just pick a refactoring and follow …

Bloaters Bloaters are code, methods and classes that have increased to such gargantuan proportions that they’re hard to work with. Usually these smells don’t crop up right away, rather …

The catalog of design patterns grouped by intent, complexity, and popularity. The catalog contains all classic design patterns and several architectural patterns.