#refactoring

Check code committed to version control for quality, and the code base will thank you.

To make something easy to understand, its parts should be at the same level of abstraction.

A deep dive into unit testing looking to answer why, how much, and what.

How to avoid “temporal dependencies” where things must be done in a certain order.

How replacing validation functions with types can make your code safer and more expressive.

Concrete tips on how to write robust tests that survive a refactoring.

An example of how moving logic and data together can result in a better design.

The need to test a private method often indicates a new class waiting to get out.

To make code easier to understand and test, try to move complex logic away from code with many dependencies.

Don’t try to test code which calls static methods, try to get rid of the static methods.