Projects focus on design and management, and these are based on coding.
Whether it is a "Project Manager", "architect", or"Program"Members" or project team members in other positions are closely related to the project. It can be said that the team members must understand this principle if they are both prosperous and damaged. Especially for project managers and architects, as a professional manager, the success or failure of a project is related to your career. For architects, you have the lifeblood of products, and you have a major responsibility as a designer for the quality of software products.
A lot of technical staff are concerned with technical points, but the more important thing is the design idea. We may wish to spend a day before developing a new system, draw "use case diagram", "activity diagram", and "class diagram" to sort out the ideas. Do not encode the Code directly. Manual coding does not save time, because if the product is not suitable, your modification process will be very difficult and is not conducive to maintenance. Therefore, before developing a new product, Please design more, think more, think more, and draw more.
During design, do not pursue patterns too much. "Because of theory and higher than theory", "no moves, no moves" should be the best choice for your own projects. Management, PM in China, mostly technical danale.ArticleThe reason why architects and project managers are put together. Management skills should be more important for a PM, such as communication, organizational, control, and leadership skills. What if a person can serve as an "architect" and a "Project Manager ???
Taking the path of design-heavy Technology and Management-heavy career.
The project leader starts the project, the Project Manager manages the project, the architect designs the product, the project team develops it collectively, and the project succeeds. This is not a simple process, in this process, we have many things to learn and start.
Apsara transmission array