Book Review : Refactoring by Martin Fowler

Brilliant book and must read one for Software engineers and Java developers. Why i emphasis this book? This book would help us to communicate efficiently. When i start reading Gang of 4 book and Head First Design Patterns, i start wondered that "hey, we did that 2 years ago and it should be called "Factory Pattern" etc etc. Giving an industry standard name for an activity is really important and it is the progression of IT industry. Once we are all familiar with naming and concept then our job is very easy to perform and make quality software. Here after i no need to explain moving method from a class to other class because of blah blah reason, just refer Martin Fowler refactoring pattern "Move Method(142)". Through out the book, i was excited to see Martin Fowler captured everything in detail related to refactoring which we facing in our day by day activity.

Nowadays IT industry code development become static, thanks to current economic downturn and baby boomer's retirement. But the software usage is exploding year by year. The software which developed during IT boom period early this decade is still in use but not scaling up with demand. The only solution now available is to refactor it and make it scalable. Not all of them afford to write a new software from scratch again thanks to economic downturn.

Refactoring by Martin Fowler gives you feeling that he is directly talking with you as a Java Architecture or a team mate. One main thing of refactor is "pairing teams" and "solid test suite". Why pairing teams is important for refactoring, we have to discuss in detail about what kind of refactoring make lot of sense. Based my experience, we have to move step by step process to achieve solid refactoring and always keep it simple.

This book gives you a in depth knowledge of refatoring and most of it, we already heard from our senior team members and architecture, i mean we already followed it because of our experience. But this book consolidated all of them and give them a name and giving some other techniques to refactoring also. Again a must read...

Comments

Vamsi said…
Good one Subba. It is a coincidence that I read this book when I had a discussion with our architects yesterday on how to formalize code reviews.
Good one Subba. Makes me want to read the book.
Thanks Vamsi, yes, it is very useful when we do code reviews.
Thanks Sukumar. Yes, you should read it.

Popular posts from this blog

Coupon Crazy

Google's Killer Application.

Uncontrolled Musing