Stumbled over the "jquery Technology Insider"

　　

The book bought February 20 this year, today is May 26, three months, in addition to the weekend rest day, if there is no special situation, I will spend two hours per night to read this book, as well as the various sources of jquery source related information. Today is always stumbled after the reading, a little excitement, but also a little disappointment-although looked, but with two words summed up the feeling is: "Confused"!

In fact, I did not really finish reading this book, because sizzle that piece I saw a little can not go on, that piece is really too troublesome. Miaov out of the video tutorial, the lecturer also admitted that the block is too troublesome, so temporarily avoid first.

After reading such a thick book (610+ page), I would like to write a long comment, but now I can not write it, because I do not really understand jquery. I am willing to share the learning process of experience to everyone, nor now, because I did not read jquery. I would like to make some comments on the jquery source code, not now, or because I did not read jquery. Have to admit, jquery source code is really difficult. It is not thoroughly understand in a short time.

In fact, I also know, want to read a book, read it again. Want to learn jquery source code, rely on this book not.

Although this book gave me the initial guidance, but I think I have been in the past few months detours, detours. Generally in the first exploration of something, there are not many previous experience guidance, detours are unavoidable. But when you're done with the detour, you'll find the shortest way. I now feel that if someone else goes to the jquery source code interpretation, must be the jquery storage structure, the relationship between data objects to the rationale. Never start with the first line of code and keep talking about the last line.

I believe most of the learners ' goal in learning jquery is to understand its design, structure and skills. According to the 8/2 rule, 20% of the code solves 80% of the demand, must have the main time, highlight the focus. For example, when it comes to CSS, we must first understand the idea that jquery solves the browser compatibility. For example, when it comes to events, it is clear that the event is stored on the cache and the storage structure of the event.

What we lack in many cases is thinking, so we will fly ourselves to the end of the Dickens struggle to learn things, and spoon-fed to teach others. It might be better if we could think of the jquery source from the jquery author's point of view. So the question we're dealing with is not just the question of which line of code is jquery, but why we have to think about jquery. What is the problem with its emergence? What are the advantages? How do we think about how this problem is designed to solve this problem? Until the end, is the source code.

I take a little time during the day to look at design patterns. At that time I tried to use the above thinking to think, the solution is surprisingly effective. Although I have not yet organized the complete design pattern, but I have tidied up, I can understand and remember. Think back to learning a lot of design patterns, learn to forget once. Wrote two articles about this blog, get a little praise, at least someone has agreed.