Why do I go to the full stack

Tag: The server publishes its own link license through ACLs for design purposes

Chulung

Original link: https://chulung.com/article/38

This article was automatically synced to Cnblogs by Metaclblog on 2016-10-25 01:00:02

Objective

Not long ago I saw this article: Why the Future is the world of all-stack engineers?
So I can immediately describe my feelings in a word: empathy.
Few an article make you feel that it is well written, but it does.

Scene

A scene:
You are a backend development, holding the front-end of the classmate's page is going to their own logic set.
You find the style is a little too right.
"Front end, this style is not ah, to see", care to think, the front end should be the fart to help you change.
However
Front-end in the meeting, the front-end is being designed, the front-end is code, the front-end to eat, and finally came back 30 minutes later, to help you solve the problem.
Assuming you know the front end, you find that the style is floating wrong, and then change it, test pass, 30 seconds.

Another scenario:
You are about to release a new beta version to the test environment, but the package is never pulled down and seems to be a network outage.
So you start looking for the OPS students.
However, the operation and maintenance of wired problems in the processing, operation and maintenance in the meeting, OPS also ate, finally 30 minutes later, he answered you, you spent 5 minutes trying to explain the situation to him. At this time another colleague has more urgent problem to operations, operation and maintenance to you say wait, 25 minutes later, he helped you to troubleshoot resetting the server DNS, you spent 60 minutes.
If you know the network and the server, you find that only the ping package is located in the domain, suspected DNS problems, after attempting to restart the server, the release succeeded, 60 seconds.

Towards the full stack

Some people say technology to go deep, everything through, everything loose. Why do I object to mentioning "full stack engineer"?
But to become an expert or to become a full stack, this is not the purpose, our goal is to solve problems, and efficient problem solving.
So instead of arguing about becoming an expert, or becoming a full stack, feel the need to make your job more efficient.
All, you can improve the efficiency of dealing with all kinds of common problems, but the difficulties always have.
Specifically, it allows you to improve the efficiency of dealing with a particular tricky problem, but it is more of a common problem at work;
Moreover, when deep into a certain level, nature will have to expand, when the knowledge is open, in fact, will want to go deep.
For me most of the time enjoy the full stack brought about by the efficient work, save time can in turn let oneself in-depth study, this state is undoubtedly the most agreeable.
So, I'm moving to the full stack.

This article is based on the Creative Commons Attribution-Share 4.0 International License Agreement published, reproduced must retain the attribution and the link.

Why do I go to the full stack