软件架构师应该知道的97件事 - CSDN资讯(国外英文资料).docVIP

软件架构师应该知道的97件事 - CSDN资讯(国外英文资料) 97 things a software architect should know It is. The following content is taken from the title of the book and gives the necessary additional instructions, which is recommended by the translator SeanBV (his CSDN blog). Customer needs are more important than Nitin Borwankar Customer demand is Paramount. Using new technology to make your resume more impressive is often counterproductive. Simplify basic complexity and eliminate the occasional complexity (Neal Ford) The analysis problem is like the cloud of the moon and the water. The key problem may not be technical (Mark Ramm). The team is of one mind. Focus on communication, stick to clear and clear expression and open leadership style (Mark Richards) Communication should be brief and precise, and dont drag the mud with water. Randy Stafford Its a good idea to plant and grow melon, beans and beans. Analyze the value of Einar Landre. The breaking of the cocoon and the sticking point. Dont be confused by surface needs. (Udi Dahan) Standing up is better. A failure will eventually happen (Michael Nygard) Preventive measures should be designed in advance to limit failure. We often lose sight of ourselves in the negotiation (Michael Nygard) Engineers should switch roles in due course and learn the skills of negotiation. (Keith Braithwaite) No rules, no square. One line of code is more valuable than the 500 lines of architecture specification (Allison Randal) The work code is the goal, the design is just a goal. There is no one-size-fits-all solution (Randy Stafford) There is no skeleton key in the software world. Focus on performance issues in advance (Rebecca Parsons) Start performance testing as early as possible. Architecture is designed to balance out the multiple requirements (Randy Stafford) Balance the technical requirements of the project and the business requirements of the relevant parties. Sloppy submission is irresponsible behavior (Niclas Nilsson) Try to put an end to the idea