Quote Baidu: All-stack engineer, also called Quantuan Engineer, English full stack developer. A person who has mastered a variety of skills and is able to use multiple skills to complete a product independently.
Want to ask now engaged in web front page and the background of the staff members of the full stack of the engineer's views, will not affect their own work or better communication to facilitate the development of the entire site and so on.
Reply content:
I am in the entry of the main to do back-end development, PHP plus database, now my work is the front end and back end of the content, superficial talk about my views.
I think all the programmers working on the web stack should be full-end engineers, and it's important and sometimes even critical to think about issues across the technology stack.
To give an example I have experienced, once in a high-traffic site of a certain function, found it difficult in the company's hardware budget with PHP and the database itself to get long-term scalability, this is the function needs real-time data of multi-dimensional screening, and to the front-end response to control within 3 seconds, The general web site should be less than 1 seconds, but the availability of this feature because of the speed of the problem, the delay is not improved (simple back-end solution we then need to use more than 20 seconds, basically not available). Finally, we get inspired by some other similar sites, in the front end with Ajax distributed shards loading data, and then distributed to run in the browser of several web workers, let them do complex data calculation, and then gradually passed the results to the main process render to the user, the process is not blocking , the single-chip data can be controlled to less than 200ms, the user basically feel the need to wait. This is a core front-end technology-based solution that is a triumph of pure back-end scenarios.
Another example is from the front-end to the back-end example, we have a relatively complex mobile application, there are two groups of about 30 templates need to render, the equivalent of the data will be used to render the 30 template, although the templates are JS precompiled, That is, there is no real-time parse problem, but we still do not want to execute too many string concatenation (compiled JS template) in Mobile, finally we move the data and the template render integration to the backend, our rest API will directly produce directly innerhtml view, the front-end only need to pass the appropriate parameters to tell the backend how to render (the full back-end view), so as to eliminate the original we have to do the front-end optimization, in this case, the optimization of the backend is much more concise.
So to become a full-end engineer is not more than a language, more familiar with some of the technology is so simple, at one end of the thinking problem and in the whole stack thinking about the difference between the problem, will profoundly affect your architecture and implementation. A lot of good development, are stuck in the cut chart ... I just want to do the front-end quietly, but I think this back-end level is really spicy chicken, or I come.
I just want to do the front-end quietly, but I think this UI level is really spicy chicken, or I come.
The development efficiency of the whole stack does not know where to go than they are. My own backend front-end database operations have been exposed, and it is not necessary to label themselves for a concept.
It used to be because small companies don't have the talent to do it. The most difficult time the company in addition to the two bosses, I and art students in the work, really no one. Later recruit two newcomers come in, just graduated, on the poor hands of the teaching! You take seriously, people still think you low level, and then all ran.
In fact, a lot of the whole stack is forced out, and later found that such work is quite efficient, and then continue to paste the entire stack of labels.
Do not do caller, the company can not go down, wages can not be opened, do not want the whole stack also have to go to the whole stack. The whole stack of engineers is a wonderful vision, but a long journey.
At present, JS has this potential, first of all it solves the problem of the front and back of the language is not unified, it uses a language to solve the problems under each scenario.
(1) JS original browser scripting language, implementation of the front-end
(2) JS has some technical solutions, even can build Android and iOS app
(3) node. JS can act as a Web server
(4) node. JS can implement back-end server
JS does do these things, but it's really hard to be able to master these 4 aspects at the same time.
The world is so big, such a master must have, but, should not be a lot.
Let professional people do professional work, division of labor to produce efficiency. If you want to implement a function (or a small application), it is not very difficult, but it is not easy to do a function to make it in every harsh scenario (large-scale access, security, good experience), but also the ease of operation, it is not a simple thing. Every aspect, behind the corresponding to a broad knowledge system, where the accumulation of accumulated technology, not to be able to easily grasp in the short term.
The whole stack may be one of the trends of the future technology, in a language/technology can solve the whole problem, which for the programmer itself is a liberation, but a heavy burden ha. Cut, we used to webmaster, that is even the design to do
It is most enjoyable to work with the whole stack (￣︶￣). Anything can be done, the efficiency has just been improved. Rob our bowl of the outfit forcing the real world of learning is not the game inside plus skill points, you can learn, you can also learn very well, to see is your personal ability and effort level.
When you reach a certain level, the whole person's perspective will vary greatly.
As for the opinions of others, there will be no strange spray, stick to what you think is right, and keep trying is what should be done. Now in the single-chip, is already a monolithic web desktop full station ...
