Intensive "Why experts do not care about the technical details."
1 Introduction
Intensive week with a feeling.
I contacted the front for eight years, to observe a lot of front-end development path of Daniel, we found that successful people have a similar experience:
Technology Initial great enthusiasm -> a lot of iconic technology projects -> turn integrated thinking -> with team / methodological concerns
That is becoming more and more experts do not care about the technical details. It should be noted that, where experts say no longer care about the details, does not mean that after becoming an expert not learn the details, nor the experts do not know the details.
Early hard to understand this shift, author visibility from the front of the school has done intensive, single-minded person is studying technology's eyes can not tolerate sand, so some of the older generation had to go to management, especially do not understand that they betrayed the front.
But the author of a gradual shift attitudes are gradually moving in the direction he himself had disgusted, I feel this is definitely not accidental, so we compiled a sentiment, hoping to prove the inevitability of this development path.
2. Intensive
First, we want a clear distinction between technicians and scientists provide technical support for the service technician is, the front end is a technology, not a science.
In addition, the development of technology to promote business needs, the state did not use scenario is difficult to promote technological progress and scientific excluded.
So technology is a business line with sustainable development, after all, we all have to eat, have a business value of the project will survive, adhering to the business of technology in order to survive, will it be possible flourishing.
This article from the three points to explain why the expert looks increasingly principles of technical details.
2.1 Technical details of the importance of the individual is changing
With the increase of years, slowly reducing the importance of the technical details, whereas the importance of technology in the field of vision gradually increase.
In the early days looking for work, the technical details are important stepping stone
University graduates that time, the technical details is an important stepping stone, only to master the technology, companies are willing to take you.
This is also why graduates do not enter a company to talk about strategy, because the time was not right.
Science and technology is not the average person can learn to work hard
Learning technologies need not be very clever mind, as long as willing to work hard, have a good ability to understand, anyone can find out the technical details.
That is, learning the technical details are no technological barriers, with increasing age, if only we can learn accumulated contents, then was eliminated when the old knowledge, learn new knowledge, speed may not be as fast young man, will gradually lose experience Advantage.
So how do you use no threshold feature, turn it into a threshold it? That is, of any age to learn the technical details are easy, you need to get into the details of time and then go in depth, does not require in-depth understanding of when to spend time on the macroscopic architecture.
Is to develop effective learning ability, can accurately determine whether there is a need to master the technical details, such as how to quickly grasp the core needs of the content, and do not yearn after the master, it can quickly extricates itself continue to think globally. This kind of thinking is the threshold of technical experts can do it.
Get things done does not have to get to know the details
At first glance a bit bizarre: do not understand the details of how to succeed?
While understanding the technical details can get things done, but do not necessarily need to be made to understand the business details.
It depends on how to understand the relationship between business and technology, such as the construction of "data federation", just to understand the technical details of the various storage systems may have to spend a long time, but in fact is not necessary to understand all the technical details are, as long as given a good general interaction specification, each storage system in line with a respective set of interactive interface to the package of this specification.
Get things done often requires macro-thinking technology, we need to link together a number of technical points. For example, to get things done is similar to command operations officer, made the purpose is to win the war through the development of play, rather than trying to charge forward and measures the width of the enemy trench. Only care about the technical details of the implementation of the final item in everyone's specific implementation of part of the technical details add up to the target is to get things done.
2.2 figuring out the true demands of business technology
Business desirable to implement functionality through technology, so the technical experts to do is how to better achieve business needs, which means understanding the business needs is the first important capability. Imagine a person can not understand what business to do, even more know the technical details, the business is of no value.
Business thinking to solve the problem, the problem is to create technology thinking
People with technical thinking, it is easy to indulge in unrealistic to solve the problem, or is someone else's problem solved. This way of thinking of technological learning is very helpful, but if you can not change this way of thinking long-term, the company is unable to create anything of value.
Owned business thinking, we must first understand the business, understand the business only, followed on business, in order for the future and confidence, knowing that their pay can be exchanged for rewards.
After understand the business, we know how to help businesses succeed through technology.
For example, in a startup company, the boss is very accurate vision into earlier time, the market is a blue ocean. After you go through the analysis, it was found to help businesses dominate the market, as long as the use of a proven technology framework for rapid iteration, we can help businesses win market in the short term. But this custom framing is not strong, if the new demand coming out reconstruction may take time. At this point people thought technology would only consider the code maintainability, proposed a set of self-development framework, and have the businesses thinking of technical experts decided to quickly make prototypes with mature technology, stable business and then reconstruct lost.
Of course, now the Internet market is very competitive, low technical threshold of Blue Ocean has basically turned into the Red Sea, the scene mentioned above may be relatively rare, we need more decision-making is whether earnings over the next few years worth of business investment in R & D resources now .
Two people will write frameworks, as a person capable of making
Another simple example is that if technical experts will become entangled in the technical details, the front-end framework to achieve a variety of well known, we can create an elegant, easy to use, maintain, and also with their "special advantage" the frame or wheels, so it is easy to fall into two teams of experts decided to butt heads in technical disputes. In this case, the output of two technical experts, even as an intern big, after all interns directly used to use open-source framework, 99% of the cases better reliability than the front wheels made their own experts.
Viewed another way, at this stage the front boundary can write React, Vue framework too many people, has been written out of the class React, frame Vue also count. In order to remove the project's practiced hand to do, really want to get people to others with still the majority, which is typical of the open source community problems: low levels of repeat-create the wheel without reason, the promotion you do not need to use responsibly. Since the frame belongs to Internet virtual assets, marginal cost is zero, which determines the framework oligopolistic market must be a big market, there can be no similar projects by some insignificant features share. So even if the write frame recruit 10 people into the corporate structure of the group, and finally only two possibilities: either bloated, everyone shows a portion of his merits to join in; or worse is to choose a program, so as not to damage any benefit of an architect.
So now companies are more inclined to internal personnel training, because the internal people understand what the business needs, value creation is often greater than the architect airborne.
Wide field of vision more easily leveraging technology
Now more and more technical point, if anything should learn more about the technical details of the final we must not have a good overall view. The state is looking for a few good insight into focus, other technical points to consider in-depth grasp of the global vision technology then.
In the early Internet, when many of the technical framework is not perfect, leveraging the technology of little significance, after all, not many things available.
But now both front-end or back-end technology, the wheels have been dazzled, can master these prior art people, has gradually larger than the value of people will complete understanding of certain technical details. Whether a good expert should be able to quickly locate to solve business problems have mature technology programs, how to achieve the minimum input-output ratio, while maintaining good maintenance maintenance business strain.
2.3 technology is not only good to be an expert in
Technical experts on behalf of technical barriers really strong man? Yes, but only technical ability is not enough.
Why open source project late looking for collaborators?
I made the initial open source projects, all frameworks and source code are hands-on, I feel that they can have a better idea than other frameworks. Few early contributors involved, of course I do not want other contributors involved, after all, they do not understand the concept, only my own modifications can make me satisfied.
Who knew him better than the author of open source projects do? Why a large open source project operation to the late, basically collaborators in the maintenance?
Because open source is a systematic thing, if you want long-term maintenance, he must establish a good filing system so that you can copy the idea, so that others can participate. If open source project only you know, it maintains two, four, six, you will certainly find powerless.
As for some people to maintain a spirit of open source big hundreds or even thousands Repo, there must be more behind the support of contributors, even if a person quit her full-time to do open source, it is difficult to simultaneously maintain more than 10 open source projects. You need to have an open mind so that more people join in, the sense of accomplishment and pride points to the number of contributors, they will continue to contribute to the project.
Resources can call in order to become an expert
The open source community project is to seize the attention of the game. Assuming that the total number of 100 open source community, your project can attract 10 people to browse, personal use 5, 2 individual contributions, will be able to basically survive. The open source community has at least 100 projects with a total number of community is not sufficient to support each project, the project can only obtain a sufficient degree of concern remain evergreen.
The same is true within the company, more experts will be asked to grade Title collaboration, we can mobilize people around and even other departments resources to play a greater value in the company.
CEO mobilized by top-level design of company-wide resources, and business line president who mobilized the entire line of business by dismantling task, through the layers of the target dismantling, and to ensure that each layer can fully mobilize all resources to the next level, companies can efficient operation.
If you have been concerned about the technical details, you will always be an isolated node, is the lowest level in the organization in any dimension, even 24 hours without sleep, also count up to two human resources. Want to break 24 hours a day limit, it must take the time to let other people agree with your design, and work toward a direction, you move on to the node, but the attendant is to take on more risk, such as distribution to others the task screwed up, the company has brought negative impact, then the person will be responsible for backing pot.
3. Summary
In summary, the point of this article is:
- Technical details of the study is not difficult, when you need in-depth insight into the best again.
- Want to get things done, you need broader technical thinking, so experts become more and more broad vision, a great pattern.
- Experts have the ability to quickly learn the technical details, but this is not their core competencies, so Instead of writing the technical details of the article, such as greater value write thinking methodology brings.
- Guide the direction is more important than walking, experts have gradually become a pathfinder.
- The final technical services for the business, understand the technical details and allow business to win is not necessarily related, so in-depth technical details before, we must first understand the business, grasp the direction, to prevent the technical details of the routing problem occurs.