My Perspective on Architects

My Perspective on Architects

2009-08-06

An architect is the soul of a project team. They determine the technical choices, overall architecture, and module division of the entire system, and may also serve as a communication bridge with leadership. In a sense, the architect largely dictates the success or failure of a project, much like the saying 'a fast train relies on its locomotive to lead the way.'

Many excellent architects evolve from excellent developers, but not all excellent developers necessarily become qualified architects. Compared to architects, the tasks undertaken by developers are relatively narrower; their primary goals include writing high-quality code, conducting thorough testing, and producing high-quality documentation. Architects, on the other hand, face a much broader scope. Beyond solid technical skills, they also need strong communication abilities and the capacity to manage the entire system from a macroscopic perspective.

Someone once said that programming prodigies in their twenties are easy to find, but excellent architects in their thirties are rare. Why is it so difficult to be an architect? Besides keen insight, I believe a good architect must possess the following qualities:

A. Solid Technical Skills. Some say architects don't need to write code, only design the overall architecture. However, I believe this is a very one-sided view. Imagine if someone doesn't write code for a long time, can they maintain continuous technical sensitivity? Of course, the 'writing code' mentioned here isn't the typical behavior of a developer, but rather about staying connected to the code. Others say an architect isn't necessarily a technical master, which I agree with, but they must be an excellent developer. B. Strong Communication Skills. This is particularly crucial because architects need to constantly exchange ideas with project developers and leadership, conveying their design intentions and thoughts. Without strong expression and communication skills, problems can easily arise. This is especially evident in companies where the communication language is not the native tongue. C. Strong Software Engineering Acumen. Although an architect is not a project manager, I believe they need a clear and precise understanding of the software development process. The 'development process' here is a general term, perhaps RUP, perhaps XP; what it is doesn't matter, but this engineering acumen is one of the essential qualities for every excellent architect. D. Broad Knowledge Domain. An architect's vision must be broad; they absolutely cannot be limited to immediate, small-scale tasks, otherwise, they risk being "short-sighted." This requires architects to continuously learn, and this learning includes technical aspects, business aspects, and communication aspects. E. Domain Knowledge. Architects must have a deep understanding of the business domain they work in. They don't necessarily need to be business experts, but they must have a profound grasp of business knowledge. It's hard to imagine an architect who frequently works on finance projects easily designing a project architecture for the telecom sector. Knowledge needs to be accumulated, and the same applies to business. F. Ability to Handle Non-Functional Requirements. Architects particularly need unique insights and solutions for non-functional requirements such as system performance, fault tolerance, and concurrency. In the later stages of a project, these issues often become bottlenecks for the entire project, and this is when the architect must leverage their strengths.

The path of an architect is arduous, full of thorns and challenges, yet it is the dream of countless developers. An architect is a synthesis of multiple skills and qualities. Every developer aspiring to this role needs to continuously improve themselves in their daily work. Here, I sincerely wish that the dream of becoming an architect can become a reality for every dedicated individual.