Based on my own understanding of technology, I have divided these levels to motivate myself to learn. Do you think this is correct?
Tool application technology level:
lv1: Easy to use in production, can fix simple bugs according to the manual or Baidu
lv2: Have a good grasp of the overall situation, and can remember the default values of most configurations
lv3: Know each configuration item The function can modify the configuration to make functional changes
lv4: Can configure tools for flexible, dynamic, distributed deployment, and high-availability operation.
lv5: Understand the basic working principle of the tool, you can carry out secondary development of the tool, and develop appropriate expansion modules according to the business.
1v6: With a deep understanding of how tools work, you can develop similar tools.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Personally, I feel that I am too biased towards [Skill]. After level 3, I need to go to [Tao]
Are we all architects in the end?(~_~)
Thank you for the invitation:
I have been exposed to development and operation and maintenance, but my knowledge is very shallow.
As far as the operation and maintenance layer is concerned, LV3 is indeed the same as what the buddy above said. The basic use of tools and the role of configuration are all fool-like learning and operations that basic operation and maintenance personnel can basically understand. After LV4, it involves the concept of architecture, how to provide a high-quality service environment, bring more profits, lower costs and higher availability to the company. As technology improves, the current needs of many software projects have If it doesn't satisfy you anymore, you have to advance to get in touch with the development business slowly, understand the working principles of the tools, and have a deep understanding of the underlying layer. So I give a definite answer. At present, the operation and maintenance layer is no longer just about playing with tools. It is more about being exposed to architecture-level thinking and knowing how to work to achieve high availability.
Forgot to add, as you advance in operation and maintenance, you will gradually become an architect.