I participated in the China Software Engineering Conference a few days ago. I was fortunate to meet Zhang Yousheng at the entrance of the venue. The strong handshake of Mr. Zhang left a deep impression on me. The venue also listened to Mr. Wen Yu's humorous and wise talk about the nine major architects. Great talk on architecture tools, increased my knowledge of architects.
I'm a programmer or software engineer and, of course, occasionally call myself an architect. Recently I have made a small discovery, that is, when many companies recruit senior technical personnel, they always put the title of architect on the position. Yes, architects are a scarce resource, especially at home. Because of scarcity, it is tall and high, and then technical personnel or enterprises are also rushing. In the end, if you are not an architect, it means that you are a code farmer with a low technical level. If an enterprise does not recruit an architect, it will appear that the unit does not have strong technical accumulation, which makes it appear No grade. In this way, the architects have become mixed, and you can see that you are an architect with deep knowledge in middleware technology when you build a Web component; you have written a small website that supports online transactions, and you are proficient in large-scale and complex e-commerce. The architect who has no more than 100,000 lines of code in his life has become a senior architect... In this way, the architect has poisoned these technicians or enterprises, and the poison is so deep that he cannot detect it and indulge in it. Can wait until the onset of toxicity to realize.
One of the toxicity of architects: without the code, the architecture is difficult to implement.
Architects are getting more and more out of touch. Others ask what architects do? The answer must be to write the plan and design the software architecture. If you want to ask him whether to write code or not, he will definitely be anxious with you. Yes, what a high-level position is an architect, how can you code like a junior programmer? Even if there are a few architects who really want to write code, vanity starts to play a role in this social environment, and these architects are forced to abandon code. As a result, the architect tossed this high-tech developer into only writing documents and drawing, and the feeling of coding has long been far away. If an architect is no longer sensitive to code, then the technical barriers to the implementation of these documents and diagrams will definitely increase.
The second toxicity of architects: as long as the requirements come in, the architecture comes out.
Here, I just borrow what Mr. Wen Yu said in the "Practice Guide for Front-Line Architects", "requirements in, architecture out", but the meanings of the two are different. What Mr. Wen Yu said about "requirements in, framework out" includes a series of method systems, including PA , CA , RA , etc. Mr. Wen pays attention to re-understanding and analysis of requirements. By toxicity I mean these architects believe that the requirements are clearly and clearly stated in the requirements specification. Yes, architects usually think that what they are concerned with is to give the architecture of the system according to the requirements document, and the requirements analysis is the responsibility of the system analyst or product manager, etc., and has nothing to do with him. Well, the architects who don't know how to analyze the requirements or the architects who are disdainful to analyze the requirements grab the nose and eyebrows, copy the constraints in the requirements specification, so that the key attributes of the system are not recognized by the customer, and ultimately fail to meet the requirements of quality and cost. , The progress is balanced, and the project fails.
Architect toxicity No. 3: Architecture for architecture's sake.
Architects forget why they need to do architectural design, it seems that it is just a routine, and a new requirement comes to their own diagrams and documentation work. As everyone knows, the core of the system is the business, and the architecture is carried out around the business. That is to say, architects have indulged in writing plans and drawing diagrams, forgetting the original intention of architectural design, and the final result is that the requirement is an enterprise website, and the architects create a large-scale distributed system model; the requirement is a Small data volume data analysis and processing tools, architects must use Hadoop . Regardless, these out-of-business architectures are undeniably failures.
Architect poisonous...
There are many more toxicities of architects, because architects have a technical decision-making role in the team. Once these toxicities occur, the impact on the project or product can be catastrophic. However, these poisons are the attributes of the architect, and there is no way to completely eliminate them, but to avoid the onset of toxicity as much as possible. Therefore, it is said that architects are poisonous, and you must keep practicing to avoid the onset of toxicity.
Author: Yi Xin, 2014-12-09 in Yangcheng.