"The Mikado method proposes a simple solution. For each change, once you find the dependencies that show errors once you make that change, create a graph that depicts these errors, along with what needs to be done to fix them proactively before actually making the change. Then you revert your change and start looking at one leaf in that graph. Fix that error, see if that causes more problems – if it does, repeat the process – continue drawing more leaves on the graph with details of what else needs to be changed, revert the entire code change, and start working on the leaf again."

understanding this and following its immediate web could probably suck up a month or two of serious time: "Conklin identifies the following as defining characteristics of wicked problems: 1. The problem is not understood until after the formulation of a solution. 2. Wicked problems have no stopping rule. 3. Solutions to wicked problems are not right or wrong. 4. Every wicked problem is essentially novel and unique. 5. Every solution to a wicked problem is a 'one shot operation.' 6. Wicked problems have no given alternative solutions."

includes a quote I hadn't heard before: '''''I am reminded of a Jerry Weinberg quote: "Things are the way they are because they got that way".'''''

simple, but difficult

stuff you don't need to know anymore -- in theory

"Change doesn't care about your investment."