• 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 ...
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • Al Hobbs
  • salvin francis

Mikado: Applicable to legacy code or new features?

Ranch Hand
Posts: 100
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ola and Daniel,

Good to see a book on a systematic approach to do code re-factoring, which I believe is a major activity happening now a days in software.

The quick introduction and the book's content seems to talk about dealing and improving legacy code. So, My question here is - Is this approach or method completely dedicated to re-factoring alone?
Or, are there parts of the approach that can be applied to new code development as well?

Thanks and Best Wishes for the Book,
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Lokesh --

Using The Mikado Method is great way to surface dependencies and it doesn't really matter if they are structural dependencies in code or things you need to take care of before something else can be done. I.e what needs to happen before a new feature is complete.

If you use it to 'drive' new features your graph might be a bit more exploratory, change more often and contain some guesswork, but not necessarily so. You can actually be very strict when you develop new features and do a lot of reverting. But usually the code is a bit more forgiving when you add to it.

So the short answer is; Yes, it can be used for new features as well as restructuring and regaining control of a messy code base.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic