What makes me think I should write another article standing on the full stack engineer is a book called Emerging Design and a word re-practise.

It seemed like a new thought, although I had already written an article called “Thoughts of the Full Stack Engineer” before that, but after half a year, I had some new thoughts. Not much has changed in the past six months, except for some soft skills like communication, expression, English, and a little technical improvement.

Every day we seem to be doing the same thing we did the day before. Life seems like a stagnant pool, adding new features and fixing old bugs day after day. The reason why we feel that life is too boring is that the existing projects are stable and will not change much — there will not be key personnel turnover, there will not be major bugs.

So naturally, we don’t need more skills to help us grow.

Personal full stack

The full stack doesn’t seem to make much sense from a personal point of view. In my opinion, I chose the full-stack route not only because it was boring to study only one thing — even though I could be a champion in this field, I have no interest in becoming a champion. And I can see the world from a new height.

Here I will suddenly have a kind of doubt – you have been drilling in a certain field, just because your work needs it!

This becomes a more interesting topic, if you don’t really like the field, how can you contribute to it? Just to let people know that you know something about the field?

And it’s particularly interesting that the tech stack you now think you’ll be fighting for is not your true love. Because you haven’t had a chance to see the world, what it’s really like, what interesting people and things there are. You chose this field just because you knew it in the past. You make a decision based on what others have told you, instead of giving it a good try yourself.

I remember when I was in school, I spent a lot of time bypassing the Java language — doing most of my thinking in Python, JavaScript (not computer science). When I got to work, I found that the language that benefited me the most was Java — because Java is such a complete language. I didn’t learn anything particularly useful from Java, but I learned a lot from books about it. Almost all books on software engineering use Java as an example, and of course some C++. Python and JavaScript satisfy my creative appetite.

Oh, and the barrel effect comes to mind. The other crazy thing about the barrel effect is that it only takes into account the length of the board, not the size of the container.

If you have more boards, you can hold more water. Similarly, if you have more technology stacks, you have more capacity. And when you start to promote one longboard, the rest of the longboard can be easily promoted.

The advantage of full stack is nothing more than learning ability and thinking ability, while bringing a broader vision.

Full stack of teams

At a large Internet company, this whole stack makes no sense. They don’t need you to have good coding skills, architecture skills, or the ability to think globally. All you need to do is get the few technical details you have right, and a 0.1% increase in performance could be worth millions of dollars. Instead, you need to master the technology stack at hand, which is dozens of 0.1%.

People on the team have the same technology stack and are talking about the same knowledge. Despite differences in ability, if one person leaves, it will bring in someone of similar ability because of the value of the role. For the big Internet companies, there won’t be too many problems.

However, as a small team, the problem becomes serious and sometimes seems overwhelming. This seems to be why pair programming has become popular abroad, even though it increases programming time and reduces the number of bugs to some extent. In fact, the advantage of pair programming is not that, but the sharing of business knowledge.

This means that in an Agile team, you have to stack. It may seem a little forced, but so do big Internet companies. You have to be an expert.

In fact, most people don’t work in just one field.



1, want to learn JAVA this technology, interested in JAVA zero foundation, want to work in JAVA. 2. Those who have worked for 1-5 years and feel their skills are not good and want to improve their skills. 3. There is also want to exchange and study together. 5. No small plus group, thank you. Please forward this article with the original link, otherwise will be investigated legal responsibility