foreword
The most effective way to improve the human efficiency of RD and QA students is to encapsulate and customize the basic components or systems, and provide a friendly interface for upper-level users (RD/QA). For RD students, they do not need to pay attention to the underlying implementation details. Focus more on your own business development.
product development system
When I first came into contact with microservices, I read an article by Amazon. As the originator of service-based systems and cloud computing, Amazon and Bezos’ forward-looking thinking is really admirable, and they put forward the concept of digital services.
Amazon started by api-based services for books and electronic resources, and provided its own internal systems or partners for use. At the very beginning, it proposed to make each service friendly to R&D from a product perspective, which has gradually evolved to By the nature of AWS, each commercial friendly service is an independent product.
In fact, many of the infrastructures we use in our daily research and development have such characteristics, such as ES, Kong, K8s, CAT and JDK, operating system resources, Mysql monitoring, Spark UI and other monitoring systems or visual scheduling operation interfaces for developers. Usable, friendly interface may also be the reason why we like to use a certain framework.
We will spend a long time to develop a basic system by ourselves. In the overall microservice system, there will be more friendly systems in service degradation, service link, slow query, public opinion information and other systems, including friendly UI interface and simple The operation button achieves the effects of one-click current limiting, flow control visualization, one-click expansion, etc., which improves the human efficiency of RD as a whole, without having to connect an SDK to develop from scratch every time, and it will not be upgraded because of the SDK version. Let the business side re-launch the version.
think like a computer
It is often seen that architects of many companies specify various usage specifications, a full set of wikis, operation and maintenance and DBA students have written various work order operation wikis, and RD students cannot avoid asking the same questions every time.
I conclude that this way of communication and cooperation is still the way of human cooperation, not the way of computer cooperation.
Putting too much normative content into the hands of people through language or wiki is unreliable in the final analysis. People make mistakes. We can give this part to the computer, and leave the right to choose. This is the best possible result.
Establishing an effective monitoring system can better help us find problems instead of drowning them in the ocean.
be happy
Some R&D students feel unhappy, I guess:
The unhappy thing may be that we have reached the Internet age, and the company is still thinking about iteration from the perspective of a software company, using the method of stacking code in large projects to face the iteration of new requirements, and manually rolling back the code and database version.
Unhappiness may be that we are in the era of big data, and we are still dealing with cognition in a basic way, just like a few years ago when we wrote a distributed multi-threaded system to do log processing and did not dare to use hadoop and spark as early adopters, so that we can Spend more time connecting with products and make cooler products.
The unhappy thing may be that we are in the AI era, and we are still logging into various OA systems, clicking various buttons, and selecting various checkboxes to submit work orders. At present, NLP, basic image recognition, and speech recognition can be used in our R&D system. , Although NLP is a field worth paying for a lifetime, simple word segmentation and similarity reasoning can be used in internal systems. Our chatops system can help us simply connect all desired R&D systems, OA systems, etc., although It is still very young, but we are thinking with the future in mind, and we are still very happy.
It should be very happy to be in the programming industry. We can help people's lives become beautiful and simple through technology. The advantage of doing a basic framework is that we can make the work of RD easier, and leave the dirty work to us. With the click of a button, you can make your system have multi-instance delivery, which can help QA students to better automate regression testing of old interfaces every time a new version is launched, reduce troubles, and framework developers will also be very happy.
Happiness comes from giving, not taking.