I spend a great deal of time, testing the hell out of my supporting material. I usually supply a GitHub repo or gist, with either a full app, or a playground.

I spend a great deal of time, testing the hell out of my supporting material. I usually supply a GitHub repo or gist, with either a full app, or a playground. In many cases, I’ll have a full app, already running, with just one source file, that we’ll be modifying. This may be in a tagged GitHub repository or gist, with tags, denoting steps[0]. In other cases, I’ll supply a zip file, with everything in it[1]. I can take a month, developing a tutorial that can be run in an hour. Teaching is hard. A good trainer spends many hours, preparing for relatively short classes. It’s sort of like playing a concert; you only get one chance, so preparation is key. Also, in tech, the students are often more accomplished than the teacher. It can be a tough room. That said, I have attended some valuable tutorials, in which the teacher did a terrible job, preparing. It’s just that I don’t work that way, myself. The main reason that I write tutorials, is to teach myself. I don’t think anyone else really pays much attention to my work[2]. I have presented a few “official” classes[1], but mostly, I work on my own. I have, actually, been teaching for decades, in small, short, seminar form; mostly for non-technical stuff. [0] https://github.com/LittleGreenViper/DemoCustomChartApp/tags https://github.com/LittleGreenViper/DemoCustomChartApp/tags [1] https://github.com/ChrisMarshallNY/ITCB-master https://github.com/ChrisMarshallNY/ITCB-master [2] https://littlegreenviper.com/miscellany/ https://littlegreenviper.com/miscellany/ (not every series is a tutorial).