Motivate a multiple do-file structure

[matthew-white]

People often zone out in 201 when we start talking about passing information across do-files via globals, args, and syntax. I've been thinking that maybe this is because they simply don't encounter this situation, because either their do-files are totally separate from each other, or child do-files don't need information from parent do-files, and don't need to send any back. I think it could make sense to spend a couple of paragraphs on situations in which this could occur, describing the benefits of many smaller do-files over a single massive do-file.

[hdiamondpollock]

Good idea Matt. This is also a good place where I think having real do-files integrated into the training could be useful..perhaps linking to something that's public on GH.

[matthew-white]

I didn't get to add as much along these lines as I would've liked. ebdd450 is a start.

[matthew-white]

I let this be a free-flowing conversation in New Hampshire, taking maybe 15 minutes. Trainees talked about times that they'd needed to pass information to/from do-files or otherwise split a do-file. Definitely better than me talking at them for the entire length of this section of the module.