Purchasing "Refactoring" by Martin Fowler

Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy.
This forum is not for asking programming related questions.

Moderator: General Moderators

Post Reply
User avatar
volomike
Forum Regular
Posts: 633
Joined: Wed Jan 16, 2008 9:04 am
Location: Myrtle Beach, South Carolina, USA

Purchasing "Refactoring" by Martin Fowler

Post by volomike »

Okay, guys, I took my $50 book certificate for Christmas and plopped it down on a used copy of Refactoring. I hope I got the right book, that it's in good condition like the owner says it is, and that the owner isn't ripping people off. Anyway, thanks for the book recommendation. I'll tell you whether I can understand the thing or whether it puts me to sleep. I hope the former and not the latter.
matthijs
DevNet Master
Posts: 3360
Joined: Thu Oct 06, 2005 3:57 pm

Re: Purchasing "Refactoring" by Martin Fowler

Post by matthijs »

Why not both? :)

and then in your dreams ingrain all that wisdom
User avatar
Chris Corbyn
Breakbeat Nuttzer
Posts: 13098
Joined: Wed Mar 24, 2004 7:57 am
Location: Melbourne, Australia

Re: Purchasing "Refactoring" by Martin Fowler

Post by Chris Corbyn »

It's a good book :) It's changed the way I write code in some ways, but much of it is just giving names to obvious scenarios too. You'll understand it... it's not an advanced subject of discussion, but it's useful to know about, especially if you're finding it difficult to maintain code.
josh
DevNet Master
Posts: 4872
Joined: Wed Feb 11, 2004 3:23 pm
Location: Palm beach, Florida

Re: Purchasing "Refactoring" by Martin Fowler

Post by josh »

You might need to keep a computer nearby to google OOP terminology from time to time but for the most part its pretty self explanatory, it shows you crappy code on one page and then shows you the refactored version on the next page, he uses this style pretty much thru the whole book. It could help to also read up on wikipedia on how to read a UML diagram ( cardinality goes on the left of a relationship line, etc... )... not required, but it'll help you understand the stuff better.
Post Reply