Becoming an architect requires experience and vision
There are two kinds of old code farmers: guerrillas and bench kings
Sitting on the bench is good for accumulating experience, not good for broadening your horizons
Traveling all over the world is good for broadening your horizons, not good for accumulating experience
The life of a yard farmer is stressful, only passion can drive you to eat apples and pick pears at the same time
Yet how much enthusiasm has not cooled over time?
Since ancient times, the pyramid structure (crowds are divided into three, six, nine, and three grades, high, middle and low) has been ubiquitous in all walks of life in human society. This is an objective law. I am afraid it will be the same in thousands of years.
Why is the pyramid phenomenon common and long-term in human society? Do other animals, such as ants and geese socialize, have them? This question is very deep, and it is difficult to get to the bottom of it. Maybe God should be asked.
The pyramid structure/phenomenon fundamentally determines that most people cannot be software architects. Not only in the software engineering industry, but only a few people at the middle and upper levels can be technical leaders.
Why most coders can't be architects
1: Coders are divided into those who can really write code and those who think they can write code.
2: Coders who can really write code are divided into those who think they are good at writing and those who are really good.
3: Coders who can really write good code are divided into those who will study and optimize continuously, and those who are content with the status quo.
4: The code farmers who can study are divided into those who like to understand the new technology in a broad sense, and those who study and use the knowledge in depth.
A small number of coders who understand breadth are willing to go deep into certain technologies, while those who like to study in depth often lack breadth knowledge.
5: Few coders who focus on depth and breadth are divided into technology for technology and technology for business.
The code farmers who are purely technical and technical have too little demand in the domestic software industry, and the demand is often not in the field of application software.
6: Code farmers who understand the depth and breadth of technology for business and need to have good communication skills.
7: And the communication is good, and some of them go to PM.
8: And the rest, some of them are gradually separated from actual development (no longer do any implementation) or start to rely on various middleware and building blocks as "architecture" means.
9: In addition to these, the rest have a certain understanding of the business, have a variety of dabbling in the breadth of technologies, and thoroughly research some technologies in depth. There is also a very important point, the consideration of issues is sufficiently detailed and comprehensive.
10: Be meticulous, comprehensive and good at communication. Technically, there is no problem with depth and breadth. I like this job and will do the underlying implementation from time to time. From the perspectives of business and development, the "architecture" is built for development efficiency and operational efficiency. , for development quality, for business flexibility and stable operation, for maintenance convenience and so on, I personally think that people can be called "architects".
And if it can really meet this demand, let alone 10%, I am skeptical that 1% can reach it. In fact, most of the current "architects" stay at these levels, and many even become architects when they reach half of the level.
Weaknesses in Knowledge Structure
Many programmers have written code all their lives, but they still do not know the underlying principles of the framework, so they cannot break through the bottleneck and step into the threshold of architects. Therefore, I summarized some knowledge systems, specially recorded the underlying principles of some architectures, and videos of source code analysis, to help some programmers break through the bottleneck and enter the primary threshold of architects. Join the group to get these videos for free 454377428
Below is the knowledge architecture diagram of the architecture:
Distributed Topics
Microservice Architecture
performance optimization
Double Eleven E-commerce Project Actual Combat
Source code analysis
team cooperation
