Refactoring: Improving the Design of Existing Code e oltre 1.000.000 di libri sono disponibili per Amazon Kindle . Maggiori informazioni


oppure
Accedi per attivare gli ordini 1-Click.
oppure
Sì, voglio provare gratuitamente
Amazon Prime!
Altre opzioni di acquisto
Ne hai uno da vendere? Vendi i tuoi articoli qui
Ci dispiace. Questo articolo non è disponibile in
Immagine non disponibile per
Colore:

 
Inizia a leggere Refactoring su Kindle in meno di un minuto.

Non hai un Kindle? Scopri Kindle, oppure scarica l'applicazione di lettura Kindle GRATUITA.

Refactoring: Improving the Design of Existing Code [Copertina rigida]

Martin Fowler , Kent Beck , John Brant , William Opdyke , Don Roberts
4.5 su 5 stelle  Visualizza tutte le recensioni (4 recensioni clienti)
Prezzo: EUR 37,24 Spedizione gratuita. Dettagli
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Disponibilità immediata.
Venduto e spedito da Amazon. Confezione regalo disponibile.
Vuoi riceverlo martedì 29 aprile? Ordina entro e scegli la spedizione 1 giorno. Dettagli

Formati

Prezzo Amazon Nuovo a partire da Usato da
Formato Kindle EUR 23,79  
Copertina rigida EUR 37,24  

Spesso comprati insieme

I clienti comprano questo articolo con Test-Driven Development: By Example EUR 29,67

Refactoring: Improving the Design of Existing Code + Test-Driven Development: By Example
Prezzo per entrambi: EUR 66,91

Mostra disponibilità e dettagli di spedizione

  • Questo articolo: Refactoring: Improving the Design of Existing Code

    Disponibilità immediata.
    Venduto e spedito da Amazon.it.
    Questo articolo verrà spedito con la spedizione gratuita. Dettagli

  • Test-Driven Development: By Example

    Disponibilità immediata.
    Venduto e spedito da Amazon.it.
    Questo articolo verrà spedito con la spedizione gratuita. Dettagli


Chi ha acquistato questo articolo ha acquistato anche


Dettagli prodotto

  • Copertina rigida: 431 pagine
  • Editore: Addison Wesley (luglio 1999)
  • Collana: Addison-Wesley Object Technology Series
  • Lingua: Inglese
  • ISBN-10: 0201485672
  • ISBN-13: 978-0201485677
  • Peso di spedizione: 1 Kg
  • Media recensioni: 4.5 su 5 stelle  Visualizza tutte le recensioni (4 recensioni clienti)
ARRAY(0xb5582e88)

Quali altri articoli acquistano i clienti, dopo aver visualizzato questo articolo?


Recensioni clienti

4 stelle
0
2 stelle
0
1 stella
0
4.5 su 5 stelle
4.5 su 5 stelle
Le recensioni più utili
5.0 su 5 stelle Necessario per chi vuole programmare seriamente 24 settembre 2013
Formato:Copertina rigida|Acquisto verificato Amazon
Un testo fondamentale per chi vuole migliorare la qualità del codice che produce o che deve intervenire su codice prodotto da altri.
Oltre alla spiegazione dettagliata di numerose tecniche di refactoring del codice, Fowler illustra come andrebbe strutturato il codice in modo che sia leggibile, comprensibile e di qualità.
Il refactoring è anche un elemento essenziale di molte metodologie test-driven.
L'unico appunto che si può fare è che il testo è di qualche anno fa per cui fa riferimento a vecchie versioni di Java. Questo però non inficia la qualità e l'importanza del contenuto.
Questa recensione ti è stata utile?
5.0 su 5 stelle Un testo fondamentale dell'informatica moderna 22 luglio 2013
Formato:Copertina rigida|Acquisto verificato Amazon
Un testo fondamentale dell'informatica moderna. È un libro che ogni sviluppatore dovrebbe leggere ed avere sempre accanto.

È diviso in due parti: una introduttiva, in cui spiega la storia e le motivazioni del refactoring, e l'altra è un catalogo di "code smells" (difetti del design del software) e di tecniche per migliorare il design del codice. Ogni refactoring è corredato da diagrammi e codice di esempio e sviluppati passo per passo.
Questa recensione ti è stata utile?
5.0 su 5 stelle Very good buy 4 ottobre 2012
Formato:Copertina rigida|Acquisto verificato Amazon
The book has a very good cover and it's printed on recycled paper. It has some useful tables for easy access and it's full of common sense well written and formalized. If you're looking for a manual this book's not for you while it can really improve your approach to code. It contains lot of things good programmers already knows, but there are many you can learn and rationalize your approach to them.
Just a soundbite:
Any fool can write code that a computer can understand. Good programmers write code that humans can understand.
Questa recensione ti è stata utile?
1 di 2 persone hanno trovato utile la seguente recensione
3.0 su 5 stelle Alcuni buoni consigli, troppe ovvietà 7 agosto 2012
Di molok
Formato:Copertina rigida|Acquisto verificato Amazon
`Refactoring: Improving the Design of Existing Code` non è un libro scritto male, ma molti dei consigli e guideline all'interno del libro mi sembrano ovvi, quindi inutili.
Ampia parte è dedicata alla reference vera e propria dei vari refactoring e sugli step meccanici da compiere per eseguirli, forse non ho capito bene il senso del libro, ma dubito che molti aprano questo libro per andare a cercare come fare un tale refactoring, anche se l'autore asserisce di farlo.
Un grandissimo buco del libro è a mio avviso la parte sul testing che viene liquidata in 15 pagine e con il commento dell'autore "questo non è un libro sugli unit test".
Per quanto mi riguarda il libro sarebbe potuto essere lungo 60 pagine; nonostante tutto qualche buon consiglio l'ho trovato (e.g. meglio non usare troppe variabili temporanee perché tendono a invogliare la scrittura di metodi più lunghi, chiamare due o più volte la stessa funzione invece di usare un temp facilita i refactoring) e ho la sensazione che tornerò a sfogliarlo tra qualche tempo.
Forse sono rimasto un po' deluso date le mie alte aspettative, è un libro consigliato da moltissima gente, un motivo ci sarà. Non costa poco e le parti veramente interessanti sono poche, quindi consiglio certamente di leggere qualche stralcio "in giro" prima di comprarlo e rimanere scottati.

Lato positivo: è rilegato e fa la sua porca figura nella libreria.
Questa recensione ti è stata utile?
Le recensioni clienti più utili su Amazon.com (beta)
Amazon.com: 4.5 su 5 stelle  171 recensioni
153 di 160 persone hanno trovato utile la seguente recensione
4.0 su 5 stelle Recipes for improving code 5 maggio 2000
Di Sean Kelly - Pubblicato su Amazon.com
Formato:Copertina rigida
Like the Gang of Four's landmark book _Design Patterns_, Fowler and his cohorts have created another catalog-style book, this time on refactoring.
Refactoring refers to taking existing, working software, and changing it about to improve its design, so that future modifications and enhancements are easier to add. _Refactoring_ is primarily a catalog of 70 or so different kinds of improvements you can make to object-oriented software.
Each entry in the catalog describes an implementation problem, the solution, motivation for applying the solution, the mechanics of the refactoring, and examples. The book's examples are all in Java, but C++ programmers should be able to approach the refactorings with ease. Often, Fowler diagrams the refactorings in UML, so a little Unified Modeling Language experience will help, too.
While the catalog is nice, the kinds of refactorings are obvious is most cases. Even moderately experienced programmers won't need the step-by-step mechanics described. The real benefit, though, is that the mechanics of each refactoring help guarantee that you can pull off the refactoring without introducing new bugs or side effects. They encourage you to take smaller, verifiable steps, than the more gross refactorings that most developers would naturally take. You actually save time doing so.
How do you know your refactorings are safe? Unit testing is the answer that Fowler et al. provide. Java developers will find the introduction to the Junit Testing Framework the most valuable part of the book, more so than the catalog of refactorings itself.
There's more to the book than the catalog and Junit, of course. There's discussion of the history of refactoring, how to evaluate refactoring tools, and how to convince management that what appears to be an overhead activity is actually useful in the long run.
Unfortunately, these sections are all too brief. And there is no discussion of how refactoring fits in with various software development processes. For example, programmers using Extreme Programming (XP) would probably feel right at home with Fowler's recommendations of refactoring in duets and unit testing, but developers stuck with a Software Engineering Institute process like PSP categorize testing as failure time and something to be minimized if not avoided. Cleanroom developers are taught that unit testing inteferes with metrics for quality, and that verifications are what should be done. Should such developers redo verifications after each refactoring? There's no answer in this book.
An unusual chapter, called "Bad Smells in Code," gives overall motivation for the refactorings. These vague notions, such as "long methods" or "lazy classes" humorously provide a foundation for starting your own refactorings. I say "humorously" because (mostly) Beck's and Fowler's odd analogies (classes becoming too intimate and delving in each others' private parts) provoke a chuckle (as if a chapter about "bad smells" in code weren't enough).
Overall, I've enjoyed reading this book and referring to the catalog while putting my own unit tests and refactorings into practice. Fowler's writing style is smooth and fluid, and it's easy to digest the catalog in no time. The book's typesetting is crisp, the figures quite clean, and both the refactoring index and "smell" index are enormously useful.
110 di 119 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Refactoring: Improving the Design of Existing Code 12 novembre 2002
Di Christopher Taylor - Pubblicato su Amazon.com
Formato:Copertina rigida
A little while back I was introduced to a word I had never heard before, Refactoring. I was told to
get Martin Fowler's book and read it so I could gain a better understanding of what Refactoring
was. Well folks, I would classify this book as a 'Hidden Treasure'.
Although it is not a flashy or well known title, I believe its impact can be much deeper and long
lasting than many of the mainstream, more popular technology books. The underlying theories
that it teaches can be applied for years, even when languages change.
There are only a couple of things I would change about this book, which I will mention below.
Preface
The Preface it brief enough, and gives the definition for the word Refactoring. This is a good thing
because right form the start you get the true definition of Refactoring. In short, refactoring is the
process of changing code to improve the internal structure, but not changing the external
behavior.
Chapter 1: Refactoring, a First Example
In this chapter Mr. Fowler tries to start by showing a simple Refactoring example. The problem is
that the chapter then goes on for 50+ pages. Mr. Fowler explains his reasons for doing this, but I
think that a simple example should have been much simpler. Especially when it is in the first
chapter of the book. It's not that this isn't a good chapter. I feel it's just too soon in the book. I
would have put it at the end.
Chapter 2: Principles of Refactoring
This is an excellent chapter. The definition of Refactoring is discussed as well as the following
questions: Why should you refactor? When should you refactor? What do I tell my manager? This
last question may seem funny, but when you read this chapter you will understand why it is in
there. This chapter also discusses common problems that occur during Refactoring, and
Refactoring and performance.
Chapter 3: Bad Smells in Code
In this chapter things that cause code to 'smell' are discussed. When code 'smells' it could be an
indicator that refactoring is needed. 22 different 'smells' are discussed. My favorites were
Duplicated Code, Large Class, and Lazy Class. This is a chapter full of awesome hints.
Chapter 4: Building Tests
Building tests is an important part refactoring. Refactoring is done in small steps, and after every
step you should test. In this chapter the discussion covers the processes and methodology of
applying tests during refactoring.
Chapter 5: Toward a Catalog of Refactorings
This chapter is a quick setup for chapters 6 to 12. Mr. Fowler explains his method for cataloging
the individual refactorings. What is pretty amazing is that he has taken a lot of time naming and
detailing each refactoring.
Chapter 6: Composing Methods
One of my favorite chapters. Mr. Fowler opens by saying, "A large part of my refactoring is
composing methods to package code properly." This chapter is all about that. 9 total refactorings
are explained. My favorite ones are Inline Method and Extract Method.
Chapter 7: Moving Features Between Objects
Sometimes you need to move things from one object to another. This chapter discusses the art of
moving features between objects. 8 total refactorings are discussed and detailed. My favorite
from this chapter is Extract Class.
Chapter 8: Organizing Data
A very large chapter that discusses in meticulous detail 16 refactorings that will make it much
easier to work with data. One thing that becomes very obvious in this chapter is that certain
refactorings can go either way. What I mean is illustrated by these two: Change Value to
Reference and Change Reference to Value. So some refactorings are not just one way deals. It
just depends on the situation.
Chapter 9: Simplifying Conditional Expressions
This is a very useful chapter since conditional logic is a common occurrence in the programming
world. Because conditional logic has a tendency to get very complex, this chapter has 8
refactorings that will help you simplify things.
Chapter 10: Making Method Calls Simpler
The 15 refactorings in this chapter help teach us how to make method calls easier to deal with.
They range from the very simple Rename Method to the more complex Replace Constructor with
Factory Method.
Chapter 11: Dealing with Generalization
Here are 12 refactorings dealing with the situations that arise from generalization. Inheritance,
Delegation, and Interfaces are some of the topics discussed.
Chapter 12: Big Refactorings
Kent Beck co-wrote this chapter with Mr. Fowler. They discuss what they call the 4 Big
Refactorings: Tease Apart Inheritance, Convert Procedural Design to Objects, Separate Domain
from Presentation, and Extract Hierarchy. These refactorings are of a more all-encompassing
type than the smaller individual refactorings from the preceding chapters. The co-authors do a
great job at putting in a nutshell what would normally take very long explanations.
Chapter 13: Refactoring, Reuse, and Reality
William Opdyke writes this chapter. He discusses his experiences with refactoring as well as
other subjects like why developers are reluctant to refactor and reducing the overhead of
refactoring. This chapter is an excellent 'putting it all together' chapter, and really helps put into
perspective the ideas that the book teaches.
Chapter 14: Refactoring Tools
Don Roberts and John Brant co-author this chapter. They discuss, as the chapter title would
indicate, refactoring tools.
Chapter 15: Putting It All Together
Kent Beck gives a quick 4-page wrap up.
One other thing I would change about the book is that I would want there to be examples in other
languages besides Java. I have practically no Java skills. For me the book would have been an
easier and faster read if it would have had examples in VB.net. Fortunately I understand enough
to get the idea of what is being taught, and that is the most important point.
Well as I said above, this book is really what I would consider a 'hidden treasure'. The things
discussed will help many people write better, more understandable code for years to come. I
would give it a 9.5 out of 10. It is well worth the {price}
27 di 27 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Making tired old code better 17 maggio 2000
Di Amazon Customer - Pubblicato su Amazon.com
Formato:Copertina rigida
The basic thesis of this book is that, for various reasons, real programs are poorly designed. They get that way for a variety of reasons. Initially well designed, extending the program may lead to software decay. Huge methods may result from unanticipated complexity. Refactoring, according to Fowler, is a function preserving transformation of a program. The transformations are reversible, so the intention is to improve the program in some way.
Fowler suggests refactoring a program to simplify the addition of new functionality. The program should also be refactored to make it easier for human readers to understand at the same time.
He also insists that each step is small and preserves functionality, and on frequent unit testing with a comprehensive test suite.
Half of the book consists of a catalogue of refactorings. He gives each refactoring a memorable name, such as "Replace Type Code with Subclasses". He illustrates the design transformation with a pair of UML class diagrams, and has a standard set of sections: Motivation, Mechanics and Example.
The Motivation is a prose section that describes and justifies the refactoring, showing the relationship to other refactorings.
The Mechanics is a sequence of steps needed to carry out the refactoring, shown as a list of bullet points He expands on some points.
The Example is where the value of this book lies. Fowler takes a fragment of Java code, and takes us step by step through the refactoring. The code is small enough that he can show it all each step of the way without overwhelming us, but is large enough to be realistic.
The code is clear enough for non-Java programmers to follow. He explains his code well enough for the book to function as a Java tutorial where the meaning of the code is not obvious. One or two of the refactorings are specific to the Java object model, and do not apply to other languages. Other languages would benefit from similar treatment, but there are very few language-specific refactorings.
The book is very much of the Design Patterns movement, with frequent references to patterns. The aim of a factoring may be to achieve a particular pattern, or it may take advantage of a particular pattern. The book can be used as a tutorial on Design Patterns.
I have a small number of complaints. Fowler advocates the use of refactoring while studying code for a code review. One needs to be very sensitive to the feelings of the programmer here, especially if he or she is a novice. The reviewer should read the code with refactoring in mind, and possible refactorings recommended, but it is for the programmer to make the changes.
Reading this book has inspired me to refactor some of my own code. My mistakes underlined the need to take small steps, and to test frequently. I spent a day building a useful Delphi testing framework from the description Fowler gives of the JUnit testing framework. The one category of code that does not seem to lend itself to this approach is some highly coupled parsing code. While I can extract small blocks of code, they remain tightly coupled with each other, and it is hard to give them meaningful names. The answer here may be to use the top down approach of recursive descent, rather than the bottom up approach of refactoring. Perhaps recursive descent can guide refactoring. Refactoring is largely a local approach. One can almost say a pinhole approach. Sometimes a global view is needed.
In summary, I would say that this very good book would be of use to Java programmers who have some understanding and much bafflement. It is very good for us older dogs who have become a little jaded and need some new ideas and motivation.
38 di 41 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Don't just read it - buy it 18 luglio 2000
Di Daniel Moth - Pubblicato su Amazon.com
Formato:Copertina rigida
One can read good books on a specific technology (COM, UML etc) or on specific programming languages or even on different approaches to software development (RUP, OPEN etc) but every now and then a true classic comes along. Like Design Patterns 4 years ago now refactoring comes along. Every serious OO developer should own both of these books. Get your hands on Refactoring if only to read chapter 3, which summarises all the 'bad smells' that may creep into code. 21 generic examples of what is bad programming and why. The remainder of the book describes numerous techniques (refactorings) for changing existing code in order to remove the 'smell'. Most refactorings are accompanied with some UML, which should be enough to get the idea, and they are then further described in Java. What makes this great a book is that it can be used as a reference very easily since its design was well thought out for this purpose with a comprehensive index and tables matching smells and respective refactorings. If any of this rings a bell to CODE COMPLETE readers it should cause the ideas are very similar but very much updated here. Fowler's writing style makes once again for easy, pleasant reading. Unreservedly recommended.
16 di 16 persone hanno trovato utile la seguente recensione
5.0 su 5 stelle Should be part of every developer's toolkit 29 luglio 1999
Di Un cliente - Pubblicato su Amazon.com
Formato:Copertina rigida
I spent seven years in the Smalltalk environment figuring (parts) of this stuff out for myself. You don't have to - buy Martin's book and shave at least a few years off the learning curve.
Refactoring is an indispensable part of software development. Like it or not, whatever you write today will be "wrong" sometime in the future. You need to have techniques for transitioning to the "right" stuff. Refactoring provides you with a wealth of small tools that can make the transition easier.
Not only that, having confidence that you can refactor your code later (supported by relentless testing) actually relieves some of the pressure you feel when you write the code the first time. Get it working, then get it right. Don't panic. Don't sweat. Enjoy your work like you did when you started (remember?). Let Refactoring guide the way.
A practical guide for any OO developer, no matter what language you are working in, though you need enough familiarity with Java to read the examples.

Ricerca articoli simili per categoria