mikado

Using a Mikado style graph for planning any large work in general has been really useful to me.

You've probably already heard of it but the mikado method can also be useful in some of these situations.

Notable exceptions are places like Mikado centers that organize tournaments and keep the old flame alive.

There's a nice Manning book from 2014 about this way of working named The Mikado Method.

Anyway, Mikado in Ikebukuro has the standard F-Zero AX cabinet, and it is great.

The thing about the Mikado method is that you’re taking what from your perspective is a top down task and flipping it to bottom up.

No that's mikado code, touch one little part and everything moves.

It goes a lot further than plan mode though, in fact I would say the key difference of mikado refactors from waterfall refactors is that you don’t do all the planning up front with mikado.

Will they do it Mikado style, or, would they say - look - we're going to tear things down and rebuild it from the ground.

In other words, I'd reword this to using the Mikado method to understand large codebases, or get a first glimpse of how things are connected and wired up.

@mikado & others: I'm curious how cinemur got started, especially investing-wise.

Mikado is more of a get out of jail card for getting trapped in a “top down refactor” which is an oxymoron.

It’s been working pretty well, still not perfect though… the tricky part is that it is very tempting (and maybe even sometimes correct) to not fully reset between mikado “iterations”, but then you wind up with a messy state transfer.

"Then the idiot who praises, with enthusiastic tone, All centuries but this, and every country but his own;" -- The Mikado 1885 US Federal Prosecutors are looking into the Mt.

You could even "enact changes upon" or "affect changes to." Alternatively, drop the extra verb altogether: "Use the Mikado Method to change complex codebases safely" > After a couple of minutes, just stop and think.

You're supposed to come up with methods like Mikado, tdd, shadowing or anything that gets the job done.

But DAGs are exceptionally good for this use case of visualising work (Mikado graphs are DAGs).

Mikado is really only powerful when dealing with badly coupled code.