On Lidor Wyssocky’s Blog on Optimizing Software Development is a post stating that you should not make your successors feel lost in your code.
Lidor uses a metaphoric story about a person being lost in a city, even though he found a map (which just *might* be of that city).
Clue is: A map is no use unless you know where you are!
Lidor concludes that having a high-level annotated map of the code (helping your successors to find out where in the code they are) reduces maintenance costs.
Sound conclusion!
