Front-end Hacker Spirit

"Full stack" before the word is very hot, although I also wrote the article said that the whole stack is actually not very reliable (the whole stack of difficult), but I would like to come back to understand why this word will cry so high.

　　Because the cost of communication between different technology stacks is too high.

Product, design, terminal, front end, backstage, OPS, test ... Seems to be able to summon the dragon, but the real possibility is that people cross over each other much longer than the actual time of doing things. Why can't all the technology be solved by one person, the manpower gets the most effective use, where has the pit to fill the person?

Interestingly, this "know what the point" of the technical staff really have, even if it is possible that the person has never touched a field, but give him a little time on the hands, it seems to be able to come up with some "still can" results come out. Then, many leader found, yes? Such people use really TM handy, and let people do a lot of heart, because many would need other technology stack intervention can solve the problem he himself can Chi Chi to take a possible more rough solution out, the whole project will feel like adding chicken blood as well to get the promotion. Facebook probably learned the sweetness, so the company pursued it as a strategy, and found that it seemed to be a really good game to go.

More and pan or few but good probably most of the technical staff have their own judgment, the whole stack of questions not discussed first, but such technical staff, on my own feelings, I am not very like to be called "full stack". Compared to the whole stack, I think it is more appropriate to use "hacker" to navigate.

　　What is the hacker spirit?

The hacker is what kind of person, I also difficult to give clear positioning, "hacker and painter" There is enough discussion, but in fact did not give a clear positioning. But at the very least, hackers have the ability to do a number of other ordinary technical personnel, among which I think the core is about two:

• Efficient Problem Solving : This may be a lot of the team will be respected, but the specific implementation of the particularly difficult, or to see the specific implementation personnel;
• Single- handedly combat : This is very interesting, many teams are in fact against such employees, think that after all, the operation of the industry has specialized, and you do other people's things are always bad, and it is easy to go into a blind spot, so that the project in a particular point into the tar pits.

So, hackers are probably a lot of teams are not very fond of, because they are difficult to control, but it is contradictory that the team would like to have a full stack, as the entire team of lubricants, in the case of insufficient (normal) situation can still allow the project to continue to advance.

In fact, does a team need to be full stack? Not necessarily, because if all the problems can be solved, who cares if you are the whole stack it? This, I think, is the essence of the whole stack of claims.

　　Front-end Hacker

I don't know if anyone else feels the same way, I always feel that the word "whole stack" will involve the front end. Probably because, from the product level, the front end is really in a very central position, and in recent years, servers, performance, algorithms and so on to the bottom of the situation, in the calculation of more and more inexpensive, performance and algorithms become more and more worthless, can be heap calculation to solve a lot of problems, the calculation can't be stored and indexed well, hit the money

But the product and experience are not the same, with a good design with enough functionality and performance, also may not be able to create a good product experience, not to mention the emergence of a variety of products between the details of the problem, a good design can not achieve the words, no meaning. This shows the value of the front end.

In the design side, the front-end can achieve the design draft, and good communication with the designer to connect? In the functional side, the front-end can be based on the actual situation to make various types of support, and optimize the transmission of the protocol and mode?

These problems are inherently possible on the design side or in the background, but the reality is that they are often adjusted and compromised by the front end. After all, this gray area has to be done, and it seems that the design side does not understand the code, and many background side think the front-end to do more convenient or simply feel that it is not related to them (such as transmission, CDN, template, data processing, etc.) ...

Not to mention, when a product is finally roughly complete, when submitting tests, the most likely problem is the front end: The compatibility and experience of the various details of the extremely complex, unlike the design side only need to tube, backstage only needs to fix the server.

At this time backstage or design side want to come over to try to do "full stack" when you will find that I wipe the pit so much, or to the front-end bar ... In turn, the front-end to try to design side and background side, but will find, eh? This world is very simple, and anyway I am not professional, get a "enough" things in the final analysis is not difficult, not to mention the industry has so many material library, background framework, tool library and so on, it seems to really do Wan Fumo Fumo opens.

　　Gradually, the front end becomes the so-called full stack:

• Design resources, it's OK, I directly take other people's color or material to fill, not good to see? Look for the designer again;
• Encounter background problems, it doesn't matter, I first get some false data to support, or just get a machine node+mongodb directly to do a DEMO, as to the throughput, to the backstage.
• Encounter operation and maintenance problems, oh, look at someone else's example to change the Apache configuration, occasionally vim to change what other configuration and then restart, as for the fine thing is not my business

But as long as it can do this, the front end has become a hacker: to the front end of the docking of other areas of the problem seems he can understand and can use their own way to carry the first, single-handedly Oh!

Do you really say that all stacks like this are full stacks? So I do not have this confidence, but also do not believe that there is a cross-type development, not only the front-end and backstage/design/operation and so on are old, this let professionals love why?

The problem is, if these other people's areas of capacity are half a bucket of water, and did not get enough accumulation, will give others what feeling? Probably is said above, we will feel this goods in a dead end, their own things do not do well on the old want to do other people's affairs, and he himself also scarcely scared: you design or interface is not ready, I do the front side also trouble Ah, this is really let people around not people. Then, of course, the whole project is still stuck in tar pits, each of them is not doing well, their side needs time, the whole team into only one person's efficiency.

In fact, the people who are awesome, hackers like the computer/Internet industry entrepreneurs, can be on the time to create conditions to be on, this is probably the hacker spirit , and now, it seems that the burden of more pressure on the front of the children's shoes.

Front-end Hacker Spirit