Build instructions, and dependency assumptions for starters. Sometimes the hardest part is just figuring out how to get a project running, or learning what kin

Build instructions, and dependency assumptions for starters. Sometimes the hardest part is just figuring out how to get a project running, or learning what kinds of settings need to be enabled on deployment. As for craft and actual in-code understanding, I think the masonry example can fit well (see pair-programming as a more fluid example of this). Granted, if you have an API, you probably want to at least document the interface with an example of how to call it. The complex bits of "how is this architect-ed can be better taught by 1:1.