Read "Large Web site technology architecture-core principles and technical analysis" one of the architects leadership art

There are always some books, so you can not stop at a glance, after reading the boiling blood, excited, like clairvoyant, such as drinking rain.

Some things, their own understanding of the 35, than others 35 words to the transparent.

Originally, the beginning should be the introduction of technology, but I decided to put the technology in the back, the beginning of the first to talk about the art of leadership. Even if you are an architect, things are going to be beautiful, but losing hearts, the end result is a failure.

Introduction to the architect's responsibilities:

Architects are a special role in the Software development Organization, in addition to the architectural design, software development and other technical work, usually need to undertake some management functions: planning product lines, estimating human resources and time resources, arranging the division of responsibilities, defining the milestone points, directing the work of Engineers, Process risk assessment and control. These management services require the participation or direct responsibility of architects who are familiar with the technical architecture of the product, the partitioning of functional modules, and the technical risks.

In the software development process, in addition to the implementation of technical architecture, the completion of product technology implementation, but also the project team and the various roles within and outside the communication coordination. It can be said that the architect has quite a lot of time to communicate with people, and dealing with the relationship between the good guys is critical to architecture and projects.

As the most senior professional technician of the project team, the architect is the predecessor of the project team development and test engineer. from the architect, the engineer can see his future, so the architect must be strict with himself in doing things, good example.

A focus on people rather than products

Be sure to believe that a good group of people do what they love and they will succeed . no matter how tortuous the process may seem, no matter how incredible the outsider looks.

So the best software project management is not to make plans, organize resources, track and revise the progress of the project, motivate and punish the members, but discover the excellent potential of each member of the project team, so that everyone understands and loves the final blueprint and vision of the SOFTWARE PRODUCT. Everyone strives to achieve self-worth, not to work for salary.

Once this is done, the team members will self-drive, consciously cooperate, find the optimal path to achieve the goal and tenacious stealth, the whole process, do not need the poor carrots and sticks. The best reward is to achieve the goal itself. The greatest punishment is that this good goal is not fulfilled.

It is also the true meaning of leadership: to find a goal worthy of common struggle, to create a work environment where everyone can maximize their self-worth.

　No lazy employees, as long as the passion has not been aroused. All managers who force employees to work overtime should feel ashamed of their incompetence.

Second, the excavation of human excellence

Expect good people to help themselves, instead of doing something to make yourself and the people involved become excellent. Excellence requires the right environment to be stimulated. Like doing something challenging, working with a better person, or having the courage to surpass yourself.

Three share the beautiful blueprint

The architect will work with all members of the project team to paint a blueprint that the team can identify with and is the goal of the team to work together.

The blueprint should be articulate: what to do, what not to do, and what business goals to achieve, all need to be described clearly.

The blueprint should be image: the product can create what value for users, what kind of market goals can be achieved, the final product will be what, the image needs to be imagined.

The blueprint should be simple: whether it's internal or external communication, there's a saying: what we're doing.

Blueprints should be written on the first page of the software architecture design document, written in the Mail's signature file, and written on the bulletin of the internal IM group.

In the course of the project, the architect will keep a focus on the target blueprint, be wary of any design and decision that deviates from the blueprint, be corrected in a timely manner, the necessary changes will be discussed, and need to be re-approved by everyone.

　　The power of the blueprint is when software developers close their eyes and see the value of the software's realization.

　　Youth always dies, and people always die. I wish my white hair look back on the past, will not do nothing for themselves and regret regret.

Four joint participation in architecture

Architects do not regard architecture as their own private property, in order to maintain the purity of the architecture and architect's without allowing others to meddle in the architecture. Let the project participants to fully debate the structure, the more we feel that they are important contributors to the project structure, the more the intention is to take responsibility for the development process, the more willing to co-maintain the structure and improve the software.

Five Learn to compromise

Architects should frankly share their design ideas, let others understand their own ideas and try to understand others ' ideas, and seek common ground to disagree.

Six achievements of others

The meaning of life is different for everyone. But for most men, the meaning is always the same: to achieve yourself. If you want to achieve yourself, you must achieve others.

Everyone has a goal of their own achievement. And work is a means of achieving self-achievement: Through the challenges of work, to explore the potential of self, re-cognition of the Self and the world.

To make a project not only to create value for the customer, for the company's profit, but also for the project members to grow. To make them feel that through this project, their knowledge and skills and business level have been improved. Let everyone think that they are important in the project, not or lack.

The architect, as the technical leader of the team, does not try to control anything in the course of the project, with a flexible plan and blueprint to advance, the team will manage their own. The more you tighten the ban, the less disciplined the team will be. The more you force, the more you cannot be independent, the more you look for help from outside, the less confident the team will be.

And once you've created a good team and you're in trouble, you can handle it, because you're not fighting alone. At the same time, a good team will also have a chemical reaction, creating a chance to surpass the job itself and create a better blueprint for the future.

PostScript: The book I finished two days, I can't stop. Really is a good book, highly recommended.

　　

Read "Large Web site technology architecture-core principles and technical analysis" one of the architects leadership art