> You also have to know what's not in the head of an absolute beginner. Then you need to fill the gaps with background material. Not too much or your audience w

> You also have to know what's not in the head of an absolute beginner. Then you need to fill the gaps with background material. Not too much or your audience will tune out. Not too little or you'll lose your audience in a puff of confusion. There needs to be just enough instant gratification to keep the reader with you. Couldn't agree more. I've spent probably a year incrementally revising a "getting started with Ruby" resource for a local software development program. [0] I ended up with a 45 minute (!!!) walk-through of how to run a test file of string manipulation exercises. [1] I treasure each of the ~500 views it's got. I spent probably 25 hours making, editing, and writing about that video. I think this video is the single most impactful thing I've ever made, in the last 10 years I've spent making things. I treasure the DMs I've gotten in Slack, from students who have found the video extremely helpful, encouraging, etc. [0]: https://github.com/turingschool/ruby-exercises https://github.com/turingschool/ruby-exercises [1]: https://www.youtube.com/watch?v=aeAkLxr5diE&feature=youtu.be https://www.youtube.com/watch?v=aeAkLxr5diE&feature=youtu.be