wood burning stoves 2.0*
The moose likes Agile and Other Processes and the fly likes Clean Code and Legacy Code Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Clean Code and Legacy Code" Watch "Clean Code and Legacy Code" New topic
Author

Clean Code and Legacy Code

Joshua Smith
Ranch Hand

Joined: Aug 22, 2005
Posts: 193
Martin-

In my place of work we have some green fields code, but a lot of it is inherited. Does your Clean Code book describe how to handle legacy code or does it assume you're architecting from the ground up?

Thanks,
Joshua Smith


Rational Pi Blog - Java, SCJP, Dev Bits- http://rationalpi.wordpress.com
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30356
    
150

Joshua,
The case studies do show well designed "legacy" code being refactored. For the "mess" that we tend to inherit, I recommend "Working Effectively With Legacy Code."


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Katrina Owen
Sheriff

Joined: Nov 03, 2006
Posts: 1358
    
  17
It doesn't focus on legacy code, but it will give you a lot of great starting points in cleaning up inherited messes.

The problem with cleaning up inherited messes, of course, is that they usually don't have automated tests.

I'd second the suggestion to look at Working Effectively With Legacy Code
Joshua Smith
Ranch Hand

Joined: Aug 22, 2005
Posts: 193
Thank you. I'll look into that book.

Joshua Smith
Robert Martin
Author
Ranch Hand

Joined: Jul 02, 2003
Posts: 76
Originally posted by Joshua Smith:
Martin-

In my place of work we have some green fields code, but a lot of it is inherited. Does your Clean Code book describe how to handle legacy code or does it assume you're architecting from the ground up?

Thanks,
Joshua Smith


Neither. It's simply a guide for transforming ugly code into clean code. The book has several examples, some small, and one reasonably large, of that kind of transformation. The book also sets for a set of traits that clean code has.


---<br />Uncle Bob.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Clean Code and Legacy Code