To open a new chapter series --JavaScript basis. Compared to the CSS series, this series of articles will be more boring boring && && boring, it is important to say the word three times.
This series of reference books are: "javaScript Definitive Guide", that is, we often say that the rhino book animal book series, so far I have read the first three chapters of content, basically not much to remember, can not think of how to introduce such a book, in my opinion, this book is like a dictionary, like, filled with many of you do not know do not want to understand the jargon, in the course of reading this book, I also found the book has also been part of the principle does not apply to the current development environment (ES6 If you are interested, you will find in this book there are many "outdated" theory). However, as the front-end developers, the book industry is still in the "Bible." Of course, you can also choose this book "JavaScript Design Patterns" from some point of view, I think the latter is more practical value, regardless of the interview or the usual project applications. Although I only saw them a few pages, but can clearly feel the latter is closer to the actual scene.
Why go to understand a "dictionary"? I used the phrase to illustrate my initial question in the title of the article. After reading three chapters, I still was not able to give a satisfactory answer. In fact, after I finished writing "CSS World" series, give myself an evaluation, after reading such a book, and after the second memory, my CSS level in the end how much progress by way of writing?
The answer is: There is progress, but not necessary. Even not read that book, I still can "experience" or a variety of loopholes to complete the layout, this layout could not very robust, however, who knows? You can do "self-righteous" feel with the draft design completely out of the ok. Even we think so, in fact, you can, if given a great product out, then you might be able to do it before reading 9 points, 1 point the rest of the whole technology, the products, and for users, you already are out, because they do not care whether your skills are good enough, they want results, not process.
Compared to the intuitive CSS, JS for user level is even more obscure, as long as your logic is correct, no one cares if you do optimization, and even if you are lazy to write more manageable range of conditions several loop nest, wrote a few less judgment, if there is no strict code review mechanism, you can still get away. There is a logic called the negatives make a positive, when I was just getting started, but also to write such a code that is used to be a bug in the code, through constant "fix", and ultimately rely on the assistance of another bug math, get the result is always correct, if not then the other question, I always thought I fix the bug, in fact I just keep trying to find in the normal operation of the system suddenly.
Compared to the white paper when just getting started, most people (including myself) impression of JS is for and if, used to write logic, knowing that writing is no big problem after the project cycle and conditions, as to what the constructor, What scope, what closures this kind of thing, ready to prepare before the interview, like, who usually nothing to seek death himself out of the dilemma? In fact, I was thinking, too, if the title of this article to give an answer, then my answer is: idle.
The beginning of each series to make their own gas: do not forget the early heart, TM really difficult.
