Martin Fowler's guide to refactoring bad code into well-structured code is an essential tool for improving the design of existing code and enhancing the maintainability of software, making it also more understandable.

Martin Fowler, a signatory of the original Agile Manifesto and a recognized leader in software management, provides a catalog of refactorings that explains:

Refactoring Data: understand the procedure and general principles of refactoring.

Identifying Code Smells: recognize the "bad smells" in code that signal refactoring opportunities.

Application Improvement: quickly apply useful refactorings to make a program more understandable and easier to change.

Creating Tests: writing good tests increases a developer's effectiveness.

Moving Features: a significant part of refactoring is moving elements between contexts.

Data Structures: a collection of refactorings for organizing data, playing an important role in programs.

Conditional Logic: use refactorings to make conditions more understandable.

APIs (Interfaces): the modules and their functions are the building blocks of our software, and APIs are the joints we use to connect them.

Inheritance: very useful, but also easy to misuse, and often hard to discern misuse until it's too late.

The examples are written in JavaScript, but it is easy to adapt the refactorings to whatever language you are using, as they mostly resemble each other across languages.

"Whenever you read [Refactoring], it's time to read it again. And if you haven't read it yet, please do so before writing another line of code." – David Heinemeier Hansson, Creator of Ruby on Rails, Founder & CTO of Basecamp

"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." – M. Fowler (1999)

Pages: 448, Dimensions: 19.2x19.2cm