The following content summarizes the internal training of Zibo Bakusha:
In the past, there was a huge gap between technology and business. When the business had needs, cross-department communication was required. The product manager would be contacted first. After the product manager refined the details, the project manager would be contacted for scheduling, and finally the development would be completed and put online.
The entire workflow not only requires a large number of people and takes a long time, but also has severe distortion at any node in the process, which will lead to uncontrollable quality in the final launch.
And because of the complexity of the R&D system itself, the entire link has to be that long.
But now with the improvement of infrastructure, especially after the FaaS architecture has become a feasible architecture, the complexity of the R&D system has been greatly reduced, and developers have more energy to move forward and get closer to the business. Thereby shortening the distance and reducing distortion.
So as a developer, how should you move forward?
I suggest you start by improving your observation skills.
As a developer who often deals with abstract concepts, the brain has been trained to think abstractly, but the real world is concrete. And it is not only concrete, but also multi-dimensional, and each dimension is concrete.
**Developers must consciously observe the concrete world and pursue feedback from the real world to avoid enjoying themselves in the abstract world. **
For example, the efficiency of picking and shipping in the warehouse was low a while ago and needs to be optimized. As a developer, how do you observe this?
Generally speaking, there are these basic dimensions that need to be observed: people, places, and steps.
Personnel: How many people are there? Who are they? How is the work divided? What is the future staff planning?
Venue: How many venues are there? Which venues are they? What will be done at each venue? What are the plans for future venues?
Steps: How many steps are there? What people and space are required for each step? How does delivery work between steps? What are the plans for future steps?
By observing the above questions, you can understand the general situation. If you find a lot of areas worthy of optimization at this level, you can start preliminary optimization.
But if you want to continue to improve, you need to look deeper into one or more of these dimensions.
For example, take the dimension of personnel: What is the height of the personnel? What is the step distance? Can the workbench and work area allow them to complete their work quickly? etc.
As you observe more deeply, you will find more and more problems and more and more challenges.
When you face and complete these challenges one by one, you will not only get real-world feedback, but also improve your abilities in all aspects, including technical abilities.
In fact, if you look at it the other way around, you will find that the FaaS architecture was actually created to solve practical problems in the R&D process. Therefore, FaaS is not only a technical architecture, but also an optimization of the entire R&D process.
So, please remember: **Pursue real-world feedback, don’t flatter yourself in the abstract world. **