So wait... You don't know what you need to know, so you want a list of things to read that will help you to learn. But you also don't know what you want to accomplish, so you want a list of lists of things to read for every possible goal, so that you can read through all of them?
Seems like it'd be simpler just to pick a topic that interests you and... search for a list covering that topic.
After reading your comments, I think you're trying to jump past the "learning to walk" stage of programming. Don't. Blogs, career advice, and CS theory are all fun to read, and will eventually be useful to you as a working programmer... But first, you really need to get comfortable just writing code. Making the computer do what you tell it. Finding out why it doesn't when it doesn't. Learning how to read (rather than decipher) other people's code, how to ask questions of it, and where to look for answers to those questions. Taking what you learn writing one program and putting it to use when writing another. Coming to the realization that your code, like everything else you write, is ultimately disposable. At that point, the essays you read on blogs, and the axioms you read in books will no longer be merely lists that you must commit to memory, but sensible conclusions that fit into your own experience (or ridiculous blather that you can dismiss outright...)
I'm not trying to be obstinate or unhelpful here, and i doubt anyone else is either... But there's a limited utility in throwing ever-longer lists at someone still beginning the long, long study that you are. When you reach the point where you could make use of a real answer to this question, chances are you'll no longer need it...