Appendix B. Setting the stage for improvements

At this point in the book, you should be pretty confident with the technical aspects of restructuring code the Mikado way. Now we’ll show you a few things that can give you advantages and boost your work right from the start. You want to make sure that you spend your time wisely and direct your energy on the essential parts of the problems.

In this appendix, we’ve gathered some tips, tricks, and good practices that can really make a difference when you restructure code using the Mikado Method. We’ll present a mix of technical and organizational advice that we’ve found very useful in solving and mitigating common problems. This appendix is organized to give you a rough hint about when the advice is most applicable—before, during, or after your restructuring. We hope you’ll find a few gems in here.

B.1. Before your restructuring

This section presents things you should think about before heading out on your restructuring. It’s a rather long list, and you probably don’t need to have them all in place before you start. Look at your context and see what needs to be done, if anything.

B.1.1. Shorten your feedback cycles

B.2. During the restructuring

B.3. When the crisis is over

B.4. Summary