We all have to work on something we hate – for most, it is working with legacy code. Nothing is more real in any job than legacy code.
How to modify legacy code? How to identify parts of the code to refactor? How to break dependencies between code you want to refactor? How to make sure the new code is doing what is expected? How do you take small steps at a time to refactor legacy code?
They are just some of the key questions answered in this brilliant book. If I have to summarise the essence of the book in a line, it would be “Write unit tests, refactor code, make sure tests are passing.”
How to modify legacy code? How to identify parts of the code to refactor? How to break dependencies between code you want to refactor? How to make sure the new code is doing what is expected? How do you take small steps at a time to refactor legacy code?
They are just some of the key questions answered in this brilliant book. If I have to summarise the essence of the book in a line, it would be “Write unit tests, refactor code, make sure tests are passing.”