How to do a good job in technology selection

As for how to use a technical framework and what scenarios does it apply to, the author suggests that you can directly read the official or corresponding github documents, and if necessary, you can also read the source code of the following concerns, so that you can understand it correctly,It is very necessary. After all, the official release is relatively authoritative, and the information in other places may be one-sided, which may be misleading to everyone's use and understanding.

In the field of software development, new technical frameworks are born and updated almost every day, and some new concepts are emerging one after another.For technical selection, I personally have the following suggestions:

1. If there is a demand, re-introduce it

In today's rich language and technical architecture, there are many kinds of components/technologies, but it does not mean that all of them should be introduced into your project. If they are simply introduced to cover the entire technology stack or components, it will beA very unwise choice.The follow-up will become a burden to your project and make you miserable.

As long as you remember these six words: "If there is a demand, then introduce", it's OK.With the improvement of the project system architecture and function, when there is a certain demand, it is gradually considering whether to introduce some technical components.

2. Select the most familiar and used technology

"It's best not to use more than 30% of new technology in a new project", I think there is some truth to this sentence.For technologies that you do not know or understand at all, you cannot predict and control any risks that will arise during the use of them. Once a problem occurs and cannot be solved within a short period of time, you will become embarrassed.

This is not to say that we refuse to use and contact new technologies. New technologies are worth pursuing, understanding, and learning. Some new technologies can bring us unprecedented benefits to a large extent, which cannot be solved by other technical frameworks.The problem.The "new technology" mentioned here refers to the technology that has not been fully investigated, technically verified, and has various doubts, but is blindly used. Such risks can be imagined.

Ensure that the selected technology is the most widely used and recognized technology in the industry, so that even if there is a problem, it can be easily dealt with.At least on a small scale within the team is very recognized.

3. Technology supported by strong community

The number of stars on GitHub is an important indicator. At the same time, refer to the update frequency of codes, documents, issues, etc. in recent years, and whether major technology blogs have related technology sharing records, which can indicate whether the technology is active and popular., How many people are used, etc.

With the technology supported by the strong community, after the selection, if there are doubts, problems, bugs, etc., there is a place to mention, repair, and explore in depth. After all, the current technology community is open enough.

Carefully choose personal open source technical frameworks, components, etc., how many pits there are, few people can tell clearly, and maybe they will cease to exist someday.

4. Starting from business and project scale

The starting point of any technology is to serve the final business. Different businesses and different project scales have different requirements for technology.For a business in its initial stage, the benchmark for model selection is relatively flexible. After all, the business is relatively simple, and the supporting business is not very large, as long as it is sufficient and the development efficiency is high enough.Projects that are reconstructed in complex business need to be selected carefully, often accompanied by the birth of some complex requirements and the uncertainty of scale. It has to be considered that the selection technology may be accompanied by some minor repairs or spiral reconstruction., you need to select a technology that is easy to adapt, switch, and replace, and has a low degree of coupling.

Because technology selection is related to business, we can observe some obvious phenomena: new technologies are often used by early-stage entrepreneurial teams or emerging businesses of large companies; the core business of medium and large companies is more inclined to use some stableTechnology that has been in use for several years; if a company uses a technology for a long time, it will tend to use it forever, even without updating the version.

Learn to think from the business side.First of all, we need to fully understand the business, understand the needs of users, understand the primary problems that need to be solved at present, and what are the possible risks, and then decompose the goals to carry out specific technology selection, model design, and architecture design.

5. Use after verification

You must be cautious about the introduction of unproven new technologies and new concepts, and you must use them on a large scale after comprehensive verification, and finally determine the type selection.The emergence of new technologies and new ideas naturally has its temptations. Being cautious does not mean being conservative. Technology is always advancing. There is no problem in embracing changes. However, introducing immature technologies seems to bring short-term benefits.The risks or later costs may far outweigh the benefits.

After verification, it will be persuasive and use more assured.

Each technical architecture has its advantages and disadvantages, and it is reasonable to exist. Different application architectures and technical frameworks are used in different business scenarios. It does not necessarily mean that the latest architecture and technology are the most suitable for you.