A question for the author of this, or other authors who create step-by-step guides like this: do you write it as you go along, or fiddle around and then go back and write the blogpost?
Even with small commits, I usually have a hard time reconstructing the history of what I've done well enough to write it up like this.
Hey there, author here. It's just me who does the entire site of pythonprogramming.net and the youtube channel.
The way I have gone about things has changed over time, but I have found the worst way to do documentation is to write 100% of the code, the full series in this case, then go back and document/write a tutorial on it.
I used to just do the videos, but had lots of requests to do write-ups too, so I started that and really hated it at first, because I was just timing it all wrong.
So now, I usually will do maybe 1-5 videos, and then make sure to do the write-ups on them before continuing...otherwise the write-ups suffer significantly. I also try to do the write-ups in the same day, and before I personally progress on to the next topics.
It's just hard, because the last thing I want to do after I've made something that I think is cool is document it.
Other times I will actually work locally, and just either save my scripts in a step-by-step manner, or just work in an ipython notebook to save the steps I took in development, and then film the video, and then go back to the notebook to do the documentation.
Not sure that really helps much, it's an "it depends," but the main thing is to not get too far ahead of any accompanying documentation.
Not the author, but usually when writing step-by-step stuff like this I alternate between short bursts of messing around and then going back to write down what I just learned.
So I'll fiddle for 10-15 minutes, occasionally pausing to write small notes and important details down (like the CLI commands I used to achieve some particular result), but only after I achieve some significant amount of progress will I go back and write about what I just did in more verbose language.
Even with small commits, I usually have a hard time reconstructing the history of what I've done well enough to write it up like this.