I must say, you have some problems with your points.
- You can make some approaches "easy" if you develop such approaches. And that is not easy. Generally, this is your choice. Whenever you want something really good, it's never easy. Your priority is your choice.
- This point it the most disturbing. I want to understand, do you want the Easy Book or the Good Book, the Most Comprehensive Book? Such things are usually different, in most book. I find wanting the "easy to understand" the most disturbing. Excuse me, why "easy"? Do you understand that the Quality and Comprehensiveness will suffer, almost inevitable. Real professionals always wants the best, not "easy". And frankly, the best professional don't really rely on the quality of books. They don't trust anything until they make sure they get first-hand understanding how things work. They don't require much of "pedagogical mastership" or quality of the text. They used to dig the truth by themselves.
Of course, a good book is good because it can save a lot of time in the very beginning. I'm not talking about this. I'm talking about your attitude. If "easy" is really your main priority, if you are scared with complexities and don't face them bravely, the whole profession is flying by you, sending you a "Good bye" message. :-)
- This item is also very disturbing. You should understand that we don't know your skills, present level, preferences, styles of work, cognitive abilities. Experience of many people shows that order of magnitude or more in performance is not so uncommon difference between different people. And still, you are asking "how much time?" What it tells me? At this point, I would question your logical thinking. Note that logical thinking is one of the most important keys in the profession.And of course your points miss a lot, miss more than they contain. One important thing is learning and understanding industrial design. Many, if not most problems found on Web development questions on this forum are related to the fact that people try to solve some problems they think should be solved, instead of questioning the problems themselves. When design is bad, no technical tricks and knowledge can improve a page or a site.
Do you want a general idea? Read this:
Peter Norvig, Teach Yourself Programming in Ten Years,
I think each student of software development should read it.
- This point shows that you probably can put heterogeneous items together, put different things in one pile. One of the major things in software development, and in engineering in general is the principles "divide and conquer" and "separate concerns". And don't think that it comes from reading some textbooks. It comes from practice, thinking, thoughtful approach to everything. Another problem with this point is: this profession really requires clearly express your ideas. And that requires regular, very systemic approach, ability to classify things, strictly formulate, and so on. This is something you should think of quite carefully. This is way more important that answering your questions.
Sorry for not answering according to your expectations. Probably, you expected to get referenced to learning materials. But your school can give you some, or some other CodeProject members can contribute. I think, this is not the most important thing. Most important thing is how you build your own learning process, how hard you try and how wise do you make some decisions on your way. A developer who just followed some schema of study, some plan offered by the school cannot be considered really good. The really good one is the one who does something else, and this "something else" part is the most important.