Classic Blunder - not committing my code

In this article, I'm doing something I should have done at the end of the last one.

Dave, you fool! You fell victim to one of the classic blunders - the most famous of which is "never get involved in a land war in Asia" - but only slightly less well-known is this: "Never stop coding for the day until you've checked in your changes"! -- slightly altered quote from Princess Bride

Ok, ok. Thankfully I didn't lose anything this time. I may not always be so lucky. There's so many ways to do this (use git) like using VSCode or some dedicated tool (eg. Sublime Merge). But this time, I'm just gonna use the command line. I know, crazy. I learned Git relatively late, just 5+ years ago, and I learned using the command line. (Git Cheat Sheet) I'll continue the narrative in the green comments on the screenshots below.

But first, I've got to activate the virtual environment....

In the next article, I'll start adding to this very blank application.

Peace be the Documented Journey!

-- Peace out!