Internal Force of Architects

When I heard about the architect, I first thought of sitting in the middle of a spacious room in a well-dressed middle-aged man looking at the landscape outside the window, and thousands of thoughts go up in my mind, there is a great deal of momentum. Programmers are architects or project managers. I recently saw a blog post by Ms. Pan zhenglei of Microsoft, which provides some inspiration.

"At that time, our team came to a newly promoted development manager. Every time I made a statement about a problem, he could not wait to propose his solution. After a long time, he still habitually suggested how to solve the problem. Through observation on weekdays, I also found that he prefers to spend time in-depth discussions on technologies and products, rather than team management. So a few months later, I took the opportunity to tell him, "I think you may be more interesting as a software architect ." He also thinks this suggestion is good. A few weeks later, he really moved to work as an architect. Our team also welcomed a new development manager ."

This example shows the profound technical knowledge of architects. Many programmers may prefer the position of Project Manager. As we can see from the above, programmers usually focus too much on technical processing details, rather than management. In this case, it seems that becoming an architect is still the final ownership of more programmers. Although the title of the project manager seems more attractive, the architect, as a purely technical position, is more suitable for the majority of programmers.

Cultivation of internal strength is not equal to the Development of dead diamonds

Speaking of the profound internal strength, everyone thought, "I am going to study the technology in the dead, isn't it all done ?". Indeed, many people understand the internal force of development technology, including language control, framework control, database management, and security management. However, we can see that more internal force of the architecture is reflected in the comprehensive use of technology. programmers who simply program can be senior programmers at most, that is, technical implementation experts.

In an interview with Mr. Wang Xiang, Senior Architect, edit 51CTO mentioned the following question: "suppose there are three outstanding programmers, A is particularly good at communication and team management. B has profound programming skills, and can quickly master new technologies. C is outstanding in terms of logical thinking and abstract capabilities. Which programmer will you train to become an architect ?"

Wang Xiang's answer is "C, which is followed by B and A in turn. A is more suitable for project managers and product managers. In addition, according to my personal experience, although the development stage of female programmers is not as fast as that of men to start with (Programmer), but can stick to Developer, S. developer, Designer, S. in the Desinger stage, their advantages in thinking ability are shown. If B is a female at the Desinger level, I would rather choose to train her because architects seem to be more suitable for women based on their personal experience in terms of creativity and knowledge aggregation ." Here we can see that the internal force is more of a kind of thinking ability, combined with the technical thinking ability. With the ability to develop programs without thinking, you can only be a code madman. If you only think about it and do not have the ability to develop technologies on the ground, you will be fooled by the performance of others.

The first layer of internal skill cultivation is naturally the cultivation of development technologies. From the beginning of writing the first line of code, I thought about why there are no other paths that can implement the same function. When we write code for a long time, should we consider more problems, such as optimization and expectations for the future. Secondly, I am familiar with the architecture. Below is a familiar Struts 2 architecture diagram. To be a good architect, you must be familiar with various architectures.

A higher level of cultivation lies in learning different technologies. Knowledge about databases, security monitoring, and network construction. This is a high-level internal practice. It is likely to have little to do with the development environment where programmers are currently working. It is not useful for programmers. However, a good architect must understand this to better abstract the software use environment and select the desired architecture and development mode.

This article is the internal force in "Ten skills for architects to fear programmers"