After reading this, I really want to know how to improve my JS programming ability.

1, learning js is divided into several stages, no entry, beginner, intermediate, advanced, ppt level.

2. How to learn without getting started?

At the beginning, I learned jquery first, with a foundation of css and html. Look at the syntax of jq is very simple, that is, the selector. It is enough for jq's api to understand high school English, and I can guess the meaning. Then I downloaded the chm manual of basic jq and read it one by one. Reading one by one is reading line by line. Don't deduct it if you don't understand. Take a look first.

After reading it, I know quite well. Oh, there is also an ajax function that can access network resources, and there is also a successful callback method that can be written. What should I do if I work overtime? How to send several at the same time? We'll talk about it later anyway. Oh, there used to be a find function to find dom nodes, a serialize function to serialize form values, a toggle function to switch, and a fn to write plug-ins. Oh, just switch cls to do this, and oh, just request json data to configure parameters.

If you understand it, you will succeed. When you use it, you will know what jq can and can't do, which chapter to read when you do it, and then study it carefully. It's a little slow to do things at first, but you'll get familiar with it after a few things.

Similarly, I study yui2, kissy, mootools, nodejs, react, ng and even swift. Just repeat it several times.

Getting started is summing up, knowing what api can do, how to do it, and talking about it when using it.

2. Beginners.

After reading the manual, I also wrote several small projects (switching classes, setting up several jq plug-ins, ajax fetching data, and putting html in the specified location). I feel so awesome that I can finally write interactive js. I feel that I am not afraid of anything, but I am just getting started.

Let's take a look at how beginners can improve their js programming skills and personal experience. Don't copy and imitate. We will use the framework tool library to complete simple requirements, but we can't understand the development principle of some complex functions. For example, a simple magnifying glass special effect, a function of cutting the head size, a carousel component, a search intelligent prompt, an at circle function, or even a fixed button to return to the top, or input box counting, form verification component, dynamic table, long connection chat function, floating layer, mobile swiper, animation function, selector, string template, rich text editor? Too much? Not much at all. I'm not finished yet. Almost all the ready-made interactions you see on the Web actually have a scientific name. Take your time, write one by one, twice and three times. Let's not talk about packaging them into components, whether the api is beautiful or not, just whether it can be written. Beginners must say no.

To put it bluntly, the accumulation of experience is a very important part of front-end development. There are some things you really can't write without writing, or you know how to write, but if you haven't written, don't say you can easily, because of compatibility problems, you still don't understand many details. So, I wrote an avatar cutting function for the first time. I've been thinking for many nights, but I just don't understand the principle. I checked a lot of articles and wrote a lot of demo, but I finally made them, but in extreme cases, there will be some bugs. Component by component, component by component, is the best way for beginners to improve.

When you know how to write any function in the basic webpage at a glance or write it yourself (not at the demo level, but at the online level), you are no longer a beginner. It takes about 1 year to get this speed up, which is why some functions have to be recruited for more than 3 years. The accumulation of experience packages can't be decided by reading a few books.

3, intermediate level.

You find that writing javascript functions is nothing to be afraid of. In other words, when measuring a demand, you never say no, but when estimating the time, you have basically reached the intermediate level. At this time, you clearly know what you are writing, you can also read what others are writing, and you have some plug-ins and components that you have accumulated and packaged yourself. So, is it perfect? You find yourself stuck in a bottleneck and don't know how to improve yourself. When you open Zhihu, you may ask this question: How to improve the advanced skills of javascript programming?

At this time, you need to take a step forward. You may be proficient in using jq or a framework, have developed cool plug-in components based on some frameworks, and have learned design patterns, some tall terms, business needs can't meet you, and automation tools grunt and gulp are used properly. In short, many things are omnipotent in your eyes. Oh, shit, why, did I Kerry win the audience?

At this time, what you need is to start thinking about your affairs from the very beginning. For example, we often like to use jq or zepto, and our plug-ins are often based on them or our experience is realized in a certain domain framework. Looking back, are these things really good? How are they realized? Why do you want to design like this? How to organize an abstract class with more than 5000 lines? Do you really understand design patterns? How much do you know about the bizarre skills of js? Have you seen some js codes that you don't understand at all? What are the big cows talking about? How many APIs does es6 have? Those novices can understand jq (really? ), why can't Mao write it himself? How on earth did grunt run? What is the source code of v8? What exactly is a test case?

Many times, when I was reading the source code of a library and reading devDependencies, I accidentally found something I didn't understand. Sometimes you laugh when you see a piece of code, and sometimes you shout. From feeling that you know everything to feeling that you don't know anything, it may be time for you to break through the bottleneck.

4. Advanced level.

Our company also has the technical sequence requirements of senior engineers, which I just praised. The basic inspection point is not how you realize a technical detail, but how you go from 0 to 1, which may involve the ability to predict 2, 3 and 4. Also, when the industry is spreading a very good and powerful thing, you can already turn it into actual productivity, find out the shortcomings of some good things, improve yourself, never be satisfied, and never worship Daniel, because you are Daniel. To put it bluntly, what you write should enable many people to solve some problems that they often can't solve, such as how to make your system faster, less dependent, smaller in code, more refreshing to develop, how newcomers can get started better, whether the api design is beautiful, and each line of code is carefully crafted, so people can put forward their own opinions at any time when reviewing what they have got. In short, legend!