• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Re-engineering?

 
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Chris and the rest of this community.

What can we expect in this book that are not covered in other ones like "Refactoring" by Martin Fowler and/or "Working effectively with legacy code" by Michael Feathers? Is it about going beyond refactoring? Is this the reason of the use of the term re-engineering?

Thank you so much in advance.
 
Sheriff
Posts: 17644
300
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes, judging from the free chapter that's available from the book's page on Manning.com, the book covers a number of aspects of a legacy project that need to be addressed besides the code. You can read more by downloading that free chapter. Click on the link at the top of this page, under the Big Moose Saloon links.
 
Author
Posts: 18
5
  • Likes 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The aim of the book is quite an ambitious one - I want to cover everything (within reason) that you can do to make a legacy project better than it currently is. This includes refactoring and tests, but that's only a part of it. I try to cover the whole package, including: quality metrics and visibility; infrastructure automation; workflow and team communication; the decision about whether to rewrite or refactor; re-architecting; and various other miscellania.

The book does have one large chapter devoted to refactoring and testing, but apart from that I've decided to leave it to the experts. Martin Fowler and Michael Feathers have already covered this topic in great detail, and there's not much more I can usefully add.
 
Marco Antonio
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you so much both of you!

To Junilu: That's true! I always forget that there are available chapters in Amazon. Thank you for your friendly reminder.

To Chris: That sounds awesome! That is what I was worried about. I'm working with legacy code and I want to carry out my job not only applying the boy scout rule or making little refactorings, I want to do a better and deeper work and your book looks like a great approach to it.


Thank you again and regards.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic