High level architecture documentation is the most-needed and least-done. Some ideas: - one piece of (longish) sample code that uses each stage. It can also be

High level architecture documentation is the most-needed and least-done. Some ideas: - one piece of (longish) sample code that uses each stage. It can also be an end-to-end test (not unit) and so forced in sync - "Design Patterns" - unpopular now, but the whole idea was common idioms so everyone can tell what you're doing. - very separate modules, with good names; interacting via simple APIs, with good names. Choose these names from outside the implementation, as if by someone who doesn't know it. The names will tell you what it is and what it does.