Refactoring is the process of rewriting software, without changing the way it functions, in order to improve its readability, testability or maintanability A book has been written on the subject by Martin Fowler Some of the chapters were written by other people Refactoring Improving the Design of Existing Code is focused on OO programming lots of Java examples and Agile practices It is setup as a catalog of refactoring techniques Each page dedicated to a refactoring is clearly marked, so that yo [...]

While this book is of a reference book than a book to read through a memorise and I intend to use it as such in the future , this book is well worth having for software engineers looking to improve their practices Even if you don t subscribe to Martin Fowler s lots of small methods and classes style of programming and I admit, it takes some getting used to , the techniques in this book are still useful and applicable to any software project The book consists mainly of a catalog of refactorings [...]

If you are interested in improving and maintaining the quality of your code this book should be on your reading list It is not the kind of book you read once and forget about it When you are doing refactoring it s always recommended to come back and check the categories explained in it What I really enjoyed is that it confirmed some of the ideas I already had about software development On the first hand you should have a robust test suite in order to be certain that refactoring didn t change the [...]

A solid book for a developer which contains a number of so called code smells , which should tell you that this specific piece of code needs to be refactored, along with techniques to achieve this result Although these techniques seems outdated as modern IDEs are able to make most of these refactorings automatically for you and these automation is described in Chapter 14 it is still good to know when to perform these refactorings.This book may be read both as a reference guide it has convenient [...]

I was having a great time reorganizing and hopefully improving some Java at work, and a coworker had mentioned this book Good stuff I didn t read through the whole reference section, but took a quick look at some It seems like the IDE I was using IntelliJ had a bunch of refactorings not sure what the overlap is with this catalog available as keyboard shortcuts, basically But it s still fun to read about Unfortunately, I got this book approximately the same week I shifted off Java development for [...]

Good way to end a year A must read reference for every developer, not only ones dealing with legacy code but ones starting new project to save the project on the long run.The book is well written, provides samples, examples, diagrams, steps to follow, side notes, commentary, and basically everything you would need to fully understand a refactoring method.While the book doesn t provide revolutionary solutions to perform refactoring you shouldn t perform major refactoring in one step anyway , a lo [...]

Finally finished this, long after the book club for it was over This is a classic, which means there are both really good pieces of wisdom in here as well as concerns that don t need to be worried about so much any with modern tools and text editors The majority of the book is kind of a reference of refactoring recipes with checklists to go through to make sure you haven t missed something time will tell if I end up using that reference portion The descriptions and motivations for performing sa [...]

Overall I was disappointed in this book Modern tools and IDE s have removed nearly all of the pain points that are laid out in this book, which made reading annoying and tiresome I skipped the Mechanics section of every single refactor because they are just not relevant in 2016 Your compiler and IDE will tell you every thing you need to know in nearly all cases That being said the content is good, albeit very basic I would recommend this to someone who is just out of college or with little to no [...]

The best programming book I ve read in a long time There are a lot of design and analysis books but not a lot of programming books I would gladly read anything from Fowler It s so simple of a concept but it goes against a lot of common sense Essentially, don t over design Don t spend too much time in design and analysis that you ve been told to do based on the wrong assumptions of the waterfall model which never worked Kent s book on Test driven Development is a great companion to this as you ne [...]

This book represents one of the building blocks of good programming Most of the examples are in java, and most of the techniques are already implemented by IDE such as IntelliJ Still, the ideas can be applied in any programming language, with or without an IDE.

I m giving this 5 stars sort of out of principle As far as I m concerned, I ve already long ago absorbed the contents of this book just by being part of the greater developer community There s lots of discussion about why you should refactor, how a good idea plus refactoring is better than full design up front, etc There s a full catalog of refactorings that you can perform, with instructions on how to do them safely with a bare text editor I think most of the refactorings are just built into ID [...]

I loved this book Martin does a great job at arguing why refactoring is so important to the software development process as a way to ensure you have the best design possible for your application, or at least aim to, at any given time That s definitely one of the things that will stick with me the most after reading this book.The refactoring catalog is presented in a very clear and concise way, going from the motivation to the mechanichs of each one, they re not hard to digest and easy to go back [...]

Excellent book about the importance and advantages of refactoring It s really made it clear for me how to not only see refactoring as a one time act of tidying up, but rather as an ongoing process.The examples provided with each refactoring are simple and short, but deliver all they need to in order to serve their purpose.I found it especially interesting to see the inverse refactorings e.g break apart a class into 2, combine 2 classes into 1 and understand that most aspects of quality code are [...]

Though it is a high rated book which is considered as a must read classic as a software engineer, I think quite a few parts are outdated This is a book written before object oriented programming totally got accepted in software industry, so lots of tips introduced can be considered as basics nowadays Also, IDEs and libraries are much smarter when comparing to 20 years before, some refactoring techniques showed in this book should get refreshed now.

This book aged very well and all it covers is still relevant today Refactoring code is a great way to preserve the value the code has while making it better at the same time Fowlers catalogue of all the refactorings not only gives us names to define a common understanding, but a practical advice on how to do it Definitively a must read for every software developer.

I found out that many patterns I used in my code were actually legit patterns discovered long before Other than that this is a pretty good documentation for working with legacy code, probably the bets one I found The format may be confusing, but I actually love it as it s quite easy to search for Overall I very much enjoyed it.

Really good book and ideas presented in it However, the book is quite old and it shows in some of the refactorings according to the book renaming variable is like rocket science Nowadays support of IDE is so good, that some of the changes are extremely straightforward and they don t really need 10 pages explanation.

It is really a good read Beware that some of concerns mentioned in the book are obsolete now, because of the IDE technologies we have now I can understand that some of the design patterns are based on this book.

I found that book quite useful and enlightening It starts with describing bad smells in code and then lists different possible refactoring in a structured way to help the reader understand when to use and how to apply them.

Good explanation when don t do refactoring and how to do that

can t say I got much out of it

A classic, it belongs in the bookshelves of every programmer.

Another gold book Must read for programmers.

Breaks down most of the things you already do in clear and easy to follow steps Good to see these refactorings as their own steps, helps in making up your mind a bit

Excellent and a must read for every professional software engineer

A great guide to learn how to systematically refactor I have recommended this book to all my peers and recommend to you, too.

A must read book for any programmer who is aspiring to learning the techniques to write clean code.

More than refactoring techniques this is a compilation of good programming practices related to how the code should be structured so even if you are just starting to code the tips would be very helpful to start with in order to avoid unnecessary refactoring in the future However if you are already in the refactoring process this book is like a check list to make your refactoring almost fool proof and can be used with any language because the principles are simplified enough to extend them to dif [...]

Skipped the actual refactorings.

Good Introduce many refactoring techniques to help write clean codeBad Some chapters 2, 3, 4, 13 is too long while the discussion is verbose, unclear, making it hard to see the author s intention.