1 of 2 people found the following review helpful
A simple technique but not really worthy of a complete book.,
Verified Purchase(What is this?)
This review is from: The Mikado Method (Paperback)
I bought this book on the description it would help refactor large code bases. The suggestions inside are really obvious and any programmer with any experience would already know it.
I can save you buying the book:-
(a) Identify the problem (part of the system you want to refactor)
(b) Draw a diagram like a flow-chart showing how to get to your goal
(c) Follow a step in the flow-chart
(d) Record (tick or cross) if the step worked
(e) Try another step or draw a new branch on the diagram
I strongly recommend getting a better book like the classic : Martin Fowler's Refactoring
Or watch any Youtube video for adding unit testing to legacy software.
Sort: Oldest first | Newest first
Showing 1-1 of 1 posts in this discussion
Initial post: 17 Sep 2014 15:18:09 BDT
Gary J. Walker says:
You forgot to mention you're working back from the ultimate target - back to the point(s) where changes fix and don't break the system. Then start back towards that target. And that you'll be mainly doing rather than analysing - breaking the system to see what more prerequisites are required, and most importantly reverting the broken system to as it was before looking at those prerequisites. Not rocket science, as they say. But a book to formulate it into a very simple methodology is useful. And this one seems to do that job well.
‹ Previous 1 Next ›