Ask HN: How should I organize my GitHub?

I am not a programmer by trade (liberal arts degree originally). Since the "Github Resume" seems to be increasingly popular, I wanted to try something else: a Github degree. By that I mean, I wanted to keep a record of every programming book I read, every exercise I do, and every project I write, and host it all on github. My purpose in doing so would be that when someone asks, "Have you ever read the K&R C book?", rather than saying, "Yes, tkae my word for it." I can say "Yes; and here are my solutions for every major exercise." This would additionally allow me to refer to past exercises for reference in future projects, and perhaps provide some kind of guide to anyone else who might be googling around for help on a particular exercise.

At this point my Github is already setup (https://github.com/AdmiralAsshat) and I've been doing this routine for every book and/or udemy course I take moving forward. At the moment most of my repos are simply named "learn_x" because I was following Zed Shaw's various Learn Code the Hard Way courses (http://c.learncodethehardway.com/), but I've since expanded to other materials.

My question primarily deals with how I should organize this stuff vis-a-vis the various books/courses. Should I divide up the repos into languages or courses? i.e. Should I give every course its own repo, or just create big "Java", "C", 'Python", etc. directories and then sub-directories for each book?

Pardon the mess on the current repos--I was learning git as I was learning the languages. I'm still trying to figure out once I decide on an organizational method how I'm going to migrate the source files while keeping the commits.