After several weeks of development, I have completed my personal project and team-end project, and a small part of my team project. After the development, in addition to improving my own capabilities, I also share some other gains and insights with you.
1. People are responsible for quality. After reading the article "people are responsible for quality: Writing to the lost generation in the market", combined with the current team projects, I think that the so-called quality, this sentence makes sense only when someone is responsible for it, and this "person" can only be one person, not several people. If no one is responsible for the development of a team together, this team is just like a piece of sand. Everyone only cares about their own part, rather than organically integrating the results of others, this is a failure, and it is difficult for such a team to complete a successful development together. However, if many people are responsible for this project, there may be some problems. For example, when other people want to report their work progress or request problems, they will not know which owner to talk, if you only contact one of them, the other person in charge will not understand the overall development progress and situation, and the other person in charge will feel uncomfortable. In addition, it is normal for various owners to have some differences, but if the coordination between them is not good (in fact, this situation should exist ), it makes it difficult for other developers to choose who to listen to, thus affecting the progress and effectiveness of the project. Fortunately, my team has a very competent person in charge, and there is no such problem between us, so we went smoothly.
2. For the development of two people, that is, our pair programming. In this way, the person in charge seems to be less important. There are only two teams, one responsible person. What is the other person called him? However, this does not mean that everyone can be lazy. Only two people can be in the same team. If one of them is always trying to be lazy, they are eager to push all their tasks to the other and enjoy their own benefits, in this way, how can we develop good applications? I think the character and ability of two people in pair programming are very important. In case of such a problem (one of them is lazy), if the other person is able to complete this task, and he is very broad-minded, if you do not care about the other party, the project of this team should be completed. However, if another person is not so powerful, and the other party does not do anything, the team will be stuck in the dark.
3. Software development is not traceable, because the environment is irregular, and the feedback process between making changes and understanding the results of changes is too long. I think it is very important in the software development process.
- Reduce the development cycle and improve the feedback efficiency, which can effectively improve the value of the software itself. By setting a small development cycle, you can make the tasks in each small stage not so redundant and complex, making it easier to keep a clear mind; improve feedback efficiency, exchange summaries in a timely manner, and improve results.
- If you want to shorten the cycle, you need to operate more or less in the multi-function team mode. The period from idea to feedback is as short as possible.
- Establishing an organization with good learning and adaptability is a very important factor. Even if some people with high abilities develop together, it will be terrible if they organize themselves. A good organization is not only capable of members, but also capable of organizing.
4. For individuals, whether it is development by one person, teaming programming, or teamwork, they need to invest a hundred percent in it. The difference in ability between people cannot be changed in a short time, but attitude is no less important than ability. It may take you three hours to get things done by others in an hour. It doesn't matter. As long as you are willing to pay, you will always make progress, but if you are just arrogant, if you think that you are too weak to others in the team, you can relax your requirements. In this way, you are not only unable to play your role in the team, but are criticized by others, it is a huge loss for you.
Read assignment 2