Software developers' "Singles" and group cooperation capabilities

Software developers' "Singles" and group cooperation capabilities

-2010-07-10

This is a topic that comes to mind when developing a pos sales system, because most people have different experiences in developing this system and have different understandings of the technologies they have mastered, the proficiency in technical applications is also different. Therefore, cooperation in cooperative development and system development is often not tacit, on the one hand, because the number of cooperation is small, and on the other hand, because of the different programming capabilities (refers to the design of the internal logic of the program, variable usage) and independent development experience are different. Therefore, everyone's capabilities need to be improved again.

This leads to the question: personal ability and teamwork ability are the key to the success or failure of software development. So is personal competence decisive or is teamwork more decisive?

I will elaborate on it through the basketball competition.

I personally feel that there is no essential difference between playing basketball and software development. Every game is a project that requires teamwork. On-site training is the hard work of software developers. The same is true.

For a game, one of the teams does not have any star players, and the main homework is usually put on team cooperation. The other team has several star players, at ordinary times, the main task is to improve the single-player capability of all players, and the cooperation part only occupies a small part.

Who will win this competition? I said that the latter will win. The former is very united. There is no doubt, but does the low level of Unity make sense? If your opponent is not united at a low level, you can win, but the opponent's level is far higher than yours. Therefore, the unity of the five may not be able to resist the breakthrough of the other two. Although basketball is a collective sport, it is also a competitive sport. Therefore, personal ability is still very important. Sometimes it is more important to pass the group. (Sometimes)

Then I went on to say that if a team is based on their individual abilities in training and then strengthens team cooperation on this basis, I personally think it is a better solution.

Return to software development.

Cooperative Development is very important because it is no longer an independent software hero. However, cooperative development should also be based on personal abilities. If your personal abilities are poor, your cooperation will be good and the final results will be unsatisfactory.

On the other hand, if we only emphasize personal abilities and neglect teamwork, we can imagine that even a product can be used in the end.

Another point is whether the training of cooperative development can also improve personal abilities?

Yes, of course, but it is only in terms of knowledge and technology. Overall control and overall thinking cannot be achieved through this, because there is no overall sense without independent development of a project.

Conclusion: team competence should be based on personal competence.

(The above are just personal opinions. You are welcome to criticize and correct them)