How to become a cool web developer

In the last two years of school, I began to develop in the direction of a web development, basically a self-taught full stack of web development engineers, from the front-end to the back end of all do, but not a proficient, see here is not very disappointed? Indeed, if it is true, I am not free to write articles here.

I've been working for more than four years now and I've just got a little bit of a knack for becoming a web developer. Dare not from Jane. A little view, share with the gentlemen.

I feel that programming, the whole is an abstract process, the world to create an abstract model, and then let them work. The abstraction of programming, is bidirectional, to the bottom, the programmer wants to abstract the realization of the computer, to the upper level, the programmer wants to abstract the complicated objective world. A higher level of abstraction is often an assembly of a lower layer of abstraction. So, the larger the system, the more abstractions it assembles.

If the computer hardware as the bottom of the program, the lower the abstraction, the ability to express the objective world is weak, the higher the high-level abstraction, the stronger the ability to express, but will lose flexibility.

Web development can be understood from this perspective, essentially working at a very high level of abstraction, because under web development, there are operating systems, browsers, interpreters, engines, frameworks, so web development has a strong ability to express the objective world.

But even so, I've been working so many years to find that the level of abstraction that we've learned in this industry has been so low that there's no big or large amount of work to be done.

So, to analyze here, I feel that if we want to turn ourselves into a cool development, first and foremost into a high-yield development, then you have to have one of your toolbox things, of course, an abstract toolbox, which should contain abstract components at all levels. After a year and a year of repetitive work, instead of taking a monthly salary, we're going to put an abstract component into our abstract toolbox. This is called accumulation.

Moreover, I think the better way is to use doctrine, do not invent it yourself. Your own invention only helps you understand the principle, but it does not help you to make a huge or numerous work results.

For example, some people ask, what language to learn, language is just an expression, its level of abstraction is low, can not help you build anything. From this perspective, language should be the simplest thing, simple to a common programmer can learn any language degree, so do not have to ask what language to learn, which easy to use, to learn on the line.

Language has a frame. Which framework is good to use, to master, and then all the development, as far as possible with this framework.

On top of the framework, there are systems and systems that need to be accumulated. Because the business model of the world, nothing but a few, once mastered all, equals you a person can build a super system out, as long as you master each system connected to it.

For example, I am a PHP programmer, and then use the YII framework, and then I mastered the CMS system, shop system, Community system, CRM system, sales support system and several other systems. Then, any new business, for the time being, is not out of these things, so I can go to help any new business to quickly produce their systems. But I found that I lacked a website or interactive performance, so I had to master a front-end framework like bootstrap to help me with the front-end performance and interaction.

Therefore, the following mode of work is to continuously accumulate various levels of abstract tools and systems. In the future, I will become a development, can handle any system development.

This is what I want to share with you.