Refactoring: Improving The Design Of Existing Code
  • Refactoring: Improving The Design Of Existing Code
  • Refactoring: Improving The Design Of Existing Code
  • Refactoring: Improving The Design Of Existing Code
  • Refactoring: Improving The Design Of Existing Code
  • Refactoring: Improving The Design Of Existing Code
ISBN: 0201485672
EAN13: 9780201485677
Language: English
Release Date: Jul 8, 1999
Pages: 464
Dimensions: 1.34" H x 9.45" L x 7.56" W
Weight: 2.29 lbs.
Format: Hardcover
Select Format Format: Hardcover Select Conditions Condition: Good


Format: Hardcover

Condition: Good

Almost Gone!
Only 1 at this price.

Select Conditions
  • Acceptable $7.99 Refactoring: Improving The Design Of Existing Code
  • Good $7.99 Refactoring: Improving The Design Of Existing Code
  • Very Good $9.93 Refactoring: Improving The Design Of Existing Code

Frequently Asked Questions About Refactoring: Improving The Design Of Existing Code

Book Reviews (10)

  |   10  reviews
Did you read Refactoring: Improving The Design Of Existing Code? Please provide your feedback and rating to help other readers.
Write Review
   Good for programmers at any level
Whether you adopt each and every one of the recommended practices, this book clearly and concisely presents each concept with examples, UML diagrams, and good explanations of the pros and cons of performing each refactoring, as well as when to use them. These are great additions to your toolset as an object-oriented programmer. Be aware that refactoring means changing a program without altering the behavior of the program, so this book can be a great aid to anyone who works with code. The book uses the concepts of patterns and a catalog to efficiently present material. It also uses the concept of smells of code to bridge the gap between intuition and best practices.
   learn object orientation from existing code
This is a must if you are new to OO programming principles. Even with the help of the book, I found it very difficult to convert from structured coding to OO coding even after reading the entire book. This book will help you look at your existing code and convert it to more object-oriented forms. Now, I just start my design and coding using my old coding practices, except that when I see an old coding style I used to perform, I stop myself and apply the recommended patterns from the book. So little by little I have grown more object oriented in my coding but by small, easily understood steps, Raymond said.
   Extremely important to all Java programmers
Pauley, Jr., said: "I simply can't say enough good things about this book. The book provides everything from advance pricing to distribution. By providing a concrete process and a wonderful set of examples that show how to turn mediocre code into great code, this book can change the way people program. Considering how many mediocre Java programs are being written today, it couldn't have arrived at a better time. I've already recommended the book and framework to my consulting clients, and will continue to do so. Thanks for the support, Martin.
   Super awesome
This is a great book. This book is the best reference I ever had for my professional life as a software developer. It has excellent advice based on years of practice with real software, not your textbook example. Once you get a few years under the belt, you find out that maintenance is where the software spends most of its life and this book contains valuable techniques to allow the software to evolve and fulfill its mission, while avoiding common pitfalls that will undermine the quality of the software before it comes to an end.
   Passable if you know what refactoring is
It is clearly outdated in a few ways, but what it isn't is a complete waste of your time. If you feel absolutely confident about knowing what refactoring is, especially if you come from Uncle Bob's Code Clean book, you can skip this.
   Open, read, close, practice, open: you would love it
Don't read it continuously, even if you think you're losing a good deal. It's best to practice before you read a pattern, or even before you do. For example, readers of the first chapter Refactoring, the first example should type the code about the 3 classes, Customer Rental, Movie, and try to improve it using their current knowledge before reading the book. Only after you have read the entire book do you know what the authors intended. You may disagree with it, but you would definitely gain more insight into refactoring by reading the book. So open the book, read, close the book, think, practice, correct, close the book, Mr. D. One needs 10,000 hours of refactoring to become a programming expert, according to some.
   One of the most useful software development books I've read
I bought this book in 2004 and have read it multiples times. The reason I bought this book was because Kent Beck was a co-author. His book, Smalltalk Best Practice Patterns, was a classic. Beck has a strong track record of successfully developing software from scratch. I've been programming for 35 years, and this book reaffirmed what I had learned from working on many projects, writing thousands of lines of code, and maintaining tens of millions of lines of code, he said. Haskell's book, "Tiny Methods," is also available at Amazon. com. However, each method must do one thing well and one method too. Avoid duplicate code, it said. If you understand and practice them, you will be a better software developer.
   Still a valuable book
The book is not just a parody, but an essential part of any good Christian mission. As a software engineering professor, I frequently lend this book to my students. The vast majority of students who borrow a copy are not asked to buy a book. His explanations are clear, his material is well organized, and his tone fosters enthusiasm. In addition, the book has been helpful to undergraduates in their second semester of programming and to advanced graduate students in their final year of study. This book is recommended for use with the Wake's Refactoring Workbook.
   A must read for every software engineer
Newer IDE's implement many of the refactorings. This support will only increase with time, so these are becoming more and more important to understand, Garton said. It's great to have a reference book at your desk, even if you're not a writer.
   A 'Must read' for professional software develoers.
However, this may be for someone dealing with a large legacy code base. But another way to look at this book is by the number of sections. The problem is, Haskell doesn't start with an anti-pattern, but with "how not to write code." It's a total waste of time, money and effort, Mr. Rule told the judge. Transform '1' to '2' and you get the illusionist effect. However, the book says these two concepts apply only to serious software developers, not to ordinary Linux programmers. But after working 25 years in multiple companies teams, I know that these mistakes are very common in many greenfield projects as well.