dandymcgee wrote:As you build on top of it and clean it up you should iteratively update the Git repo so that anyone using it to learn can go back and look at your history if they want. If you're trying to preserve the simplest possible project, you could fork it for the more complex version.
That's the plan, actually.

Keep every iteration of the project available, so if someone wants they can step through the evolution. I know the project is really simple, but I think it's a valuable illustration.
When I was first getting started (as a clueless teenager) the lack of "finished" examples/usage code for most libraries was a hurdle. "Here's how to load an image" vs. "Here's how to link all these subsystems and APIs together to make something cohesive."
As you gain experience, you reach a point where basic examples (and
Reading
The
Fucking
Manual) is enough to make you comfortable, but as a programming virgin it's daunting to slog through documentation and trying to make sense of it with no frame of reference. Hopefully this will help someone past that.