The second semester of software engineering finally ended before entering the third year. This semester was less than two weeks old, and the project period was shorter. In the security field, the subject matter was more professional, and the team leader was under more pressure. However, this short-term and efficient Android Application Layer development and learning has also laid the foundation and confidence for myself and my projects, and given me a mental preparation for my upcoming junior year, and, again, let me explore what is my own limits, And what technology is willing to bear.
1.Team up.
Every time I team up and team-mates, I hope to have a good relationship and atmosphere. After all, individual conflicts will inevitably hinder the project progress. However, contradictions are inevitable, but they are not irreconcilable. The role played by the captain is a little greater here. When taking into account the individual's self-adjustment ability, they must actively participate in the overall grasp and coordination. Good communication and communication can promote the harmonious and stable play of each person in the team. A good team leader depends on his own abilities, and on suitable team members and teammates. In fact, when the team leader is under a lot of pressure, I still expect the team members to say "I understand", whether you understand it or not. The better zxh is, the greater the ability, the greater the responsibility. Its own Java programming foundation is not a general water, Android development is also a fur, as the captain will have to improve their awareness and attention at all times. Grasping the overall situation and overall view, supervising the development progress, and mobilizing enthusiasm, the team leader's role in these aspects is not big or small, but they are the key to a team spirit.
2.Code.
My point of view began to shift from mutual learning and mutual digestion among project team members to focusing more on engineering closeness and efficiency first. Software that can work is better than comprehensive documents. Splitting a question into a relatively independent module by a relatively independent division of labor. Through a relatively independent test, the agile development model may be an optimal solution for efficient production. Programming and learning for Android and Java is just a plug-in. The Java learning that comes into use at the beginning of the second semester is totally useless. During the summer vacation, the android beginner project also played a guiding role. However, through this physical project's self-attempt, we have achieved a new level of perception for past things. This may be close to the development model of the lab or R & D job in the future. Which task should be used to identify the knowledge and use the instance module and product to supplement the practical experience on unfamiliar knowledge, instead of deep learning a language or standard. It is true that 21 days of study... And in-depth introduction... We have to adopt appropriate selection strategies based on our actual situation.
3.Stress, night farming, and others.
The stress of this time is mainly due to fear of unfamiliar technical fields, slow pace of advancement, and mismatched progress of various modules of the project, in the middle section, the programming design of the non-communication part of the client is also one of the sources of pressure. Fortunately, this time, my teammates were not so tired about preparing for the PPT due to their separation of document reports, and the short schedule did not increase the pressure. The only night of night flushing mainly focuses on the improvement and optimization of the client's functions. The last night's night-flushing plan was stranded because I got up early all day and didn't take a nap, on the same day, the acceptance and demonstration programs were also cool, sleep, and getting up early. The captain needs to rest.
Each team-Project Collaboration may bring different technical and interpersonal experiences. We now think that programming is not a technical activity, but a physical activity. Maybe it will be more like this in the future. The most important and difficult part of a clear task indicator is to parse the architecture, model, and algorithm module. The core of teamwork is still the division of labor. If the division of labor is good, cooperation is good. Finally, I would like to thank my teammates.
If you decide to be a good programmer, please give up the game unless you are the kind of genius that can write a good program every day as long as you play the game. Share with every former, present, and future teammate.