Post #1010243

Making "don't perform premature optimization" more rigorous: First, you need to graph the formal coboundary of your problem. Only once you've done that is it safe to contract your graph around your actual obligation cells. This is often called "waterfall". If the problem is moving too fast to do that, you need to start with a smaller part of the problem, but apply the same rigor. And then compose, gluing the next cell, which you will have constructed equally rigorously. *This* part is called "agile".