The key points of "Working Effectively with Legacy Code"

Struggling with Legacy Code and not enough time to clean it up?

can help you rescue any codebase quickly and safely !

“Legacy Code is code without tests”

If you’ve come across that definition, it’s from Michael Feathers’ book: Working Effectively with Legacy Code.

While I have a slightly extended definition, this is a very valid and useful one!

Feathers’ book is from 2004. Yet, its content doesn’t get outdated. There is a reason for that and this CommitStrip puts it best:

This book is a reference. Probably THE reference.

When there’s a thread about Legacy Code, it doesn’t take long for someone to drop a comment suggesting you read it.

I didn’t read it. I’ve seen it’s recommended. But what are the key points of that book?

If that’s you, I got your back!