Mikado Method Essentials
In preparation for my last post Mikado Method to install a Vim Plugin I just had to read one of the good articles about the Mikado Method again. And when something really grabs my attention and I think there are relevant things in such an article (or video) I usually tweet the things I find most essential. So here is a collection of (some of) the things I find most relevant in that article.
Related tweets
"...a naïve change, you realize that the system is not built for the type of change" Mikado Method #ftwhttps://t.co/Y7ED60qk9v
— wolframkriesing November 5, 2017
#mikadoMethod is a great way to do what @KentBeck said: "make the change easy, then make the easy change"https://t.co/Y7ED60qk9v
— wolframkriesing November 5, 2017
"It’s time to get back to the last known good state."
— @wolframkriesing November 5, 2017
Don't fear deleting code, fear deepening the rabbit hole!https://t.co/Y7ED60qk9v
"By avoiding analysis paralysis and too much guessing, you let the feedback be your compass"https://t.co/Y7ED60qk9v
— wolframkriesing November 5, 2017
"By working the Mikado graph from the leaves in, you can perform big changes while keeping the system in a deliverable state, all the time."
— wolframkriesing November 5, 2017
Mikado method can help you morphing systems to a new better shape, staying in a deliverable state.https://t.co/Y7ED60qk9v
— @wolframkriesing November 5, 2017