Not only can she cobble it together - it has to be something that helps her feel a sense of pride, dignity, and understanding. Some guides get someone to "the

Not only can she cobble it together - it has to be something that helps her feel a sense of pride, dignity, and understanding. Some guides get someone to "the end", but they don't scaffold an understanding of the underlying principles, and the student feels even more confused at the end than at the beginning. I always go to great lengths to show the mistakes that I make all the time, and to show how much of a given domain I don't know. For example, in a Make an OSS contribution walk-through I did, I mention over and over how myself or the senior dev I was pairing with didn't understand something. [0] Most of the job of a modern software developer seems to be surfing across an ocean of complexity, avoiding everything except the _one specific issue_ we're working on. To persons unfamiliar with the field, they might think that we actually understand everything to any degree of depth. They would be deeply mistaken. [0]: https://intermediateruby.com/matt-swanson-jekyll-bug-p2 https://intermediateruby.com/matt-swanson-jekyll-bug-p2