This week's book giveaway is in the Other Languages forum.
We're giving away four copies of Functional Reactive Programming and have Stephen Blackheath and Anthony Jones on-line!
See this thread for details.
Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Clean Code and Legacy Code

 
Joshua Smith
Ranch Hand
Posts: 193
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34973
379
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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."
 
Katrina Owen
Sheriff
Posts: 1367
18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 193
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you. I'll look into that book.

Joshua Smith
 
Robert Martin
Author
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic