Is there an end to the learning path of Web development?

On the road of web development, I will comfort myself when I am overwhelmed by the deep sense of the world: Hold on, one day I will get through the two meridians (front end + back end)

In fact, this is not a piece of my experience, but just to put my own problem set out, I hope through the text to help comb under.

Write and think there is a big difference, write it out and read it first, as if the new ideas with their own dialogue, ideas collide with a new idea, modify the re-write, is indeed a help "deep-seated" thinking, thinking in the end of a good way.

The following words are the final idea left after the deletion of n times, I believe that later back to see there will be different views.

Since stepping into the internet development of the road (since 2013.3), the vast, ever-changing open source technology so that I have a study plan obsessive-compulsive small white often fall into such a dream dimple: Plan more, implement less, learn not finish.

Read a blog post in open source China this morning. Should you be a full-stack engineer?

One of the authors gave such advice:

If you want to move in the direction of a full stack of engineers, you should have a lot of knowledge and skills, and be familiar with the various components mentioned above.

In addition, you need to improve your personal communication skills so that you can manage and collaborate better with front-end and back-end developers.

The good news is that the future is bright for every type of web developer, whether it's the front end, the back end, or the full stack.

Keep learning all things that are valuable, learn new frameworks, languages and platforms, and communicate effectively with developers and end users.

In this case, you will remain invincible no matter what happens in the world.

OK, the endless Internet technology is beyond doubt, what should I do?

Individual projects/Team projects-project positioning

The "All-stack engineer" often discussed in the programmer's circle, in my opinion, first of all, there must be a precondition, "why" to do the full stack?

• (individual) purely to learn to practice the Internet [the most popular new technology], then this "all-stack engineer" is really difficult, it takes a lot of time and effort to keep up with the "trend", Basic skills list:

  • Linux/git/pip/npm/composer ...
  • Apache/nginx
  • Mysql/mongodb/redis.
  • Php/python/nodejs
  • Javascript/jquery/expressjs/angularjs/reactjs ...
  • Html/html5
  • Css/css3/saas
  • Browser development tools and debuggers

• (personal) To implement an item (assuming it's just a website), it's easy to define the schema based on the project type and your own skills, and set the "one stack"

  • Lamp+bootstrap Heavy back end light front end
    • Linux/git/pip/composer ...
    • Apache/nginx
    • Mysql
    • Php/python
    • One day Getting Started Bootstrap library
  • mean+thinkphp Heavy front light back end
    • LINUX/GIT/PIP/NPM ...
    • Mongodb/redis.
    • nodejs/php
    • Javascript/jquery/expressjs/angularjs/reactjs ...
    • Html/html5
    • Css/css3/saas
    • Browser development tools and debuggers
    • One day introductory thinkphp frame
• (team) is a commercial mature project, both front and back are very heavy
  • Front-end engineers [in-depth] mining the most current front-end tools and libraries, responsible for the front-end performance, building their own front-end framework according to their own project business
    • My ability is limited, I do not list
  • Back-end engineers [in-depth] study high concurrency and data performance, responsible for back-end performance; Build your own back-end framework based on your project business
    • My ability is limited, I do not list

Note that the "Basic Skills" list is listed above, and the list length and skill depth should be doubled if the large-scale projects are commercialized, and of course, in a large project, every engineer does a daily job of a project, such as paying, and he's going to study the API of each payment channel.

Therefore, to understand their current work status, project status, business status, to the team/project to set a good position.

OK, my current position is ...

If not, the daily study list is not finished, it is taken for granted because your goal is messy, a will want to realize their own idea, a will think of a company's business, a friend to help do the site.

Front end? Back end? Full stack? – Skill Positioning

Skill positioning, which can be largely cut off from the learning list (I think it's less than 50%)

For example, positioning the front end, do not go too much to dig nginx,php.

Instead of locating the back end, don't go to the angulajs,backbone.

Position full stack ...

I'm talking about all-stack engineers.

The popularity of the all-stack engineer, in my cognition, mainly has the following aspects to promote the factor:

• The popularity of the Nodejs ecosystem has allowed some front-end engineers (especially the backend to master the node-to-front) to naturally position themselves as full stacks
• A very powerful front-end UI library such as Bootstrap makes it easy for back-end engineers to build a web system
• At present, the Internet entrepreneurship is popular, most start-up companies in the initial project development phase, will want to have a full stack development engineers to save labor costs

The separation of the front and back end, to a large extent I think it is because the "front-end" split out, and in today's user experience-oriented environment occupies the same importance as the "back end" status. But on the other hand, with the rapid development of technology, with the increasing complexity of operations, services and frameworks have their own characteristics, it is difficult for a person to master all the skills. There are several years of experience in the front end, or back end, from a certain aspect, can call themselves "full stack", but from the more stringent aspects, few people can truly "advance with the Times" of the "full stack"

Remember the first one that brought me to the back end development told me: style/special effects are not necessary to study, others a wget have been taken, concentrate on the backend bar.

That was the beginning of 13, the front end should not have a special fire, unlike the current recruitment h5,h5,h5 ... So, understandably, the backend would despise the front end. But now, how dare you?

Front-end engineers, both in terms of job difficulty and salary, have pressed the back end a little.

Said despise "front-end", there is a "pseudo-front-end" phenomenon: in the front-end engineers talent gap, many artists ui/just graduated from the training course, directly applied to do the "front-end"; Do not understand Linux, do not understand node, do not understand the front end of sass, to tell the truth in second-tier cities such as Wuhan, really a catch a lot.

Pull so much, if you still want to locate the "full stack" (specifically the following one), it is necessary to increase the daily learning time of 3 hours to prepare it ...

• (individual) purely to learn to practice the Internet [the most popular new technology], then this "all-stack engineer" is really difficult, it takes a lot of time and effort to keep up with the "trend", Basic skills list:

OK, my current position is: Do not toss, do a quiet beauty backend bar.

A few principles of perseverance

The lessons of these years, I think are also valuable, in the future is to unswervingly follow:

• Think your own, programmers still have to have their own programming ideas
• Write more, good writers don't cherish words like gold
• Run code up, not just knock it out
• Show me your project, practice and practice, there is no way to test the effectiveness of learning than to participate in a specific project
• Resolve it now, the problem is solved! Can't drag! Can't drag! Can't drag!

Learn any language/frame/library, must have a "project" as the carrier;

Whether it's a project you want to get this skill from, or because you have an idea to learn the various skills that support project, it's OK.

Welcome to the author's new blog: www.ganiks.me

Written in the last

For a long time did not write their own ideas, write this hundreds of words actually took me 3 hours. Many of them want to write Wuhan Optics Valley's Internet development and whether programmers should do outsourcing such topics, next time.

