The scenario in this paper is aimed at entrepreneurial teams and traditional enterprises with a business-focused, non-technical R&D background.
Thought that the function realization is the whole of research and development.
Functional implementation is actually just the initial technical work. Some non-technical bosses and entrepreneurs want R&D personnel to realize the functional characteristics of a certain product, and believe that the completion is all and everything is done. In fact, this is only the first step in the long march. A lot of outsourcing development is limited to feature implementation.
Technical problems after the function is implemented, at least include the following
First, performance and load support capabilities. How many types of requests can be supported by the user, such as how many times per second, how many times the order is placed, how many orders of data can be supported, and how large. The performance bottleneck will occur in what size of data and what size of request.
Second, stability and fault tolerance.Whether it can be in abnormal input, abnormal network environment, the system remains stable and healthy, and will not cause system crash and avalanche effect due to some sporadic abnormal requests or network anomalies.
Third, system security and disaster backup system. Intrusion risk, hacking risk, and even if the intrusion leads to a repository, whether there is a disaster recovery mechanism and the ability to maintain sensitive information is not so easy to obtain.
Fourth, sustainable maintenance. Whether the subsequent upgrades, maintenance, and substitutions can have sufficient maintenance guarantee. Whether it can achieve low coupling and high multiplexing, can easily expand to support new business types.
A common hallucination, I have a cool idea that others have not realized.
If you are based on business capabilities, most business claims can be done through third-party products, but many entrepreneurs will feel “I have a cool idea, others’ open source systems are not implemented.” In fact, I think so many times. But unfortunately, in most scenes, these cool ideas are too wishful. They haven’t even studied the open source products, and maybe the product’s setup options have long been compatible with their ideas, but they haven’t even looked at them.
Many entrepreneurs don’t know how much the cost of paying for this self-righteous idea. They are only for some negligible feature improvement, some self-righteous small innovations, and bear the incomparably heavy research and development costs. More critically, the quality of the products developed, their code quality, stability, and sustainable maintenance are far less than those of third-party open source software that are widely used and recognized. Therefore, not only did it cost a lot of money, but it was still a very unusable product, and the lost time cost was hard to measure.
Know a master can beat the world.
Some entrepreneurs will say that they have found a well-developed background, a technical manager or even a director of a large company, so they are confident in their own research and development.
First, R&D is not a person who fights the world. Of course, such talents also exist, but in most cases, the client and the server are matched by different technical personnel.
Second, the R&D masters of large companies are not suitable for startups because a considerable proportion of R&D managers in the background of large companies will not save money.
Third, people are liquid. Long-term sustainable maintenance of the system requires an alternate successor at all times. And the entrepreneurial team, this condition is basically not available.
Fourth, the cooperation between R&D and products requires long-term running-in, as well as considerable specifications and routines. And many entrepreneurs with non-R&D management backgrounds don’t even understand the responsibilities and scope of work of product managers. Without a product manager, it is difficult to make good products with good R&D. The entrepreneur will think that I am very clear about an idea or need why he does not understand it.
R&D and maintenance become a bottomless pit.
Still remember the premise, you have the business ability and need to have a technical product to carry your business. Quite a part of the situation, not warm or not bad is the norm of many business operations teams. At this time, you have a R&D team, you may find that the cost ratio is very high, but if you give up this product, then the sunk cost is not reconciled, you said to minimize the maintenance of technical support, then upgrade, repair holes, system expansion, etc. The problem will definitely be endless.
Many R&D teams led by business-oriented companies, such as dealers and agents, always want to do some research and development by themselves, or some traditional brand manufacturers want to engage in Internet marketing. They want do their own APP and mall, and many of them will go to the above situation.
If you are doing content operations, e-commerce, traditional industry network marketing, in fact, there is really no need to do any research and development, there are many ready-made third-party tools can be used, and you can focus more on the business itself.
Why choose third-party tools instead of outsourcing?
Third-party tool developers have the advantage of scale and can have better programmers. In terms of performance security, it will be far better than the average level of outsourcing. Third-party tools have a lot of customer experience and lessons, so you can step on a lot of pits. You can focus on the business and you can quickly try and try. The trial and error costs are low and the time cost is low. The version update is maintained for a long time, and the subsequent expansion capability is far better than the outsourcing development.
Mature third parties have experience in the friendliness of search engines and giant platforms. WordPress and Shopify are highly friendly on Google. Inexperienced development teams simply don’t know where these skills and boundaries are. It’s easy to do more and more wrong.
So, how should third-party tools be chosen? In fact, it is very simple. From the probabilistic point of view, the most users and the most abundant peers are generally not wrong.
Is this unfair to small and beautiful third-party teams? Probability, if you have a strong technical judgment, of course, you can judge according to various evaluation data and actual measurement. If you don’t have the ability, don’t be too convinced of your judgment.
Perhaps the demonstration of this small team is in line with the needs. But what about stress testing, safety testing, fault tolerance testing, and wind control testing?
Of course, in the top few in the market, you can also make some choices and choose a higher degree of business fit. This can be decided according to your own business, but it is recommended not to choose tools and products that are too cold.