Summary of China Software Engineering Conference

Today, I attended the annual China Software Engineering Conference. I have heard many brilliant speeches from my predecessors on the stage. Next, I will summarize several important speeches and finally write my own experiences.

 

Project Manager leadership

Speaker: Tian junguo

1. Leadership and leadership
   There is no direct relationship between the two. Many leaders are often led by their subordinates.
2. Consensus and target sharing
   The story of moving a ladder vividly explains the importance of sharing a target with subordinates.
3. Communicate with the iceberg
   Only a small part of an iceberg is exposed on the water. Only SUPERFICIAL communication is usually not the most direct and cannot achieve the purpose of communication well.
4. Be a highly self-respecting person
5. Balloon Principle
   To be a leader, at least your balloon should be able to accommodate your subordinates.
6. Coach
7. Snoop Weights
   Similar to Jin Mu water and fire, Renyi Li Zhi Xin.

 

Software Enterprise FAQ and systemic solutions

Speaker: Lin Rui

 

 

Nature of demand

Speaker: Xu Feng

 

Architecture Reconstruction

 

Author: Wen Yu

 

Personal Summary

 

I think there are some gains in these two games in the afternoon.

 

In the first session, we will talk about the demand side. I have never caught a cold eye on demand, but this is the first time I have heard such an interesting speech from the demand side. The exploration process of demand can be integrated into 1.1 drops of life. The problem-level description and solution-type description must be separated to better explore the needs. When talking with customers, the demand analysts must have a deeper understanding of their needs. The degree of understanding of the business determines who leads the business.

People live to benefit the society and bring value to others. To bring greater value, we need to understand the needs of the target audience at a deeper level so that we can exert our capabilities and make more meaningful contributions. This is what I think this speech is of the greatest significance to me. When thinking about various goals in the future, we can use the "problem/SOLUTION" model to achieve a deeper goal.

 

The later part is the architecture reconstruction mentioned by Mr. Wen Yu. In fact, the speech he most expected to hear when he went to ccse2010. I have read his "Software Architecture Design" before and think it is very pragmatic and instructive. There are few such high-quality books in China. Although the architecture reconstruction mentioned in this article is not entirely a new viewpoint, it is exactly the same as what I have done, so I also hear it with relish. According to instructor Wen, restructuring must be divided into: Architecture restructuring, module restructuring,CodeRebuild. I have been in the company for more than a year now. Although I have not implemented architecture-level reconstruction, I am doing reconstruction in about half of the time, code reconstruction and module reconstruction. Although many issues need to be considered for restructuring, more responsibilities and more pressure are required, I am still happy. First, in the current project team, the original architect was busy with other work, while other colleagues were not familiar with the structure of the system at the moment. Therefore, restructuring is my responsibility. Secondly, this is related to my character. I have always been "code obsessive-compulsive disorder", and I think there is still room for optimization. I think it will be even more painful if my colleagues do not refactor their tasks now, I will stick to what others think and what they say ...... I read an article a few days ago.Article: The 20 dead ways of the reconfigurator are well written, but I may have laughed at these problems. There are many things, if you want to do it, you have to bear the difficulties.

If you really want to have a job as a "design reconstruction engineer" in the future, you can try it ......

 

Finally, let's talk about career planning. Looking at the great predecessors on the stage, it is true that a sword has been worn out for ten years. During my lunch, I asked my friend, "many ancient heroes have been famous in the rivers and lakes after years of deep mountain cultivation. If you have ten years, which direction will you choose to cultivate? How do you feel if you have reached the level of talent on the stage ten years later ?"

In fact, I want to ask myself this question. Although I have always been passionate about technology, and now I feel that the technology is not bad, but if I want to practice it in the future, I am depressed. Because I like technology, it doesn't mean that I like technology for my whole life, even architects. Going home at night, I chatted a lot with my girlfriend about career planning, interests, and life. Finally, I came up with some conclusions, which made my girlfriend feel a pity, because she always thinks that I am a technical material.

If I don't do anything, I will regret it when I look back ......