A project of GITHUB address
https://github.com/DN-C/IdeaSharing
II. Consideration of the problems encountered and summary
1. division of topics and problems encountered:
1: In the beginning of the project, the first problem we encounter is the project topics, topics involving organization to have a stronger ability to coordinate the students do, but who will do the team leader, how to choose the problem is the biggest problem.
2: After determining topics, among some other members of our professional turn, some high-grade (I) how coordination among members is a big problem, not familiar with each other, how better to exchange collaboration is the second major problem we encountered.
3: In the division stage, we are not too high enthusiasm, to mobilize the enthusiasm of the team, it is another problem facing.
2. The way to solve the problem:
1. Because I was the initiator of the team, so I chose to be a team captain, my captain, although a bit tricky.
2. Contact inconvenient problem after we met through the line, and then determine the tasks to do each achieved in this way, we make a record of each meeting, on target to be completed determination, make online communication aid.
3. division stage a little rough. . . I personally bear record of each meeting, blog maintenance, and front-end interface picture production, interactive and background by the team responsible for internal staff together, although seemingly have division of labor, division of labor but slightly confusing.
Stage division of the problem is removed, the code on GitHub related aspects, the question is more, although we contacted, but most are exposed to, but not how to make good use too, for some functions, it is generally not familiar with the issue number of small, fuel Figure also do not submit.
Think
This project gave me the most feeling then is how to mobilize the team internal motivation, how we can each play to their talents is a very important thing, personal humble opinion, be aware that the basic situation within the team members, what he is good at, suitable for what,
What are the disadvantages. Only clear on their own within the team members, in order to give them a better space to play to their talents.
III. Improved team division
Initial confusion caused by the division of labor is more overall progress is more bureaucratic, but also made a further division of labor in about eleven weeks, but clearly everyone's job, blog management, GitHub maintenance work, front-end code to write, write and write code behind the corresponding database
Specific division of labor, their duties, although sometimes a bit chaotic, but overall more organized. If still areas for improvement, then, is the current division of labor because of capacity constraints we are now a lot of people involved in both writing code and testing the background, everyone has a job, but
Is not completely independent, is not an independent development and independent testing. Which I think we can improve.
IV. Code Specification
In the early days, because everyone has their own style of writing code, variable names, function names, etc. are different, some people with the alphabet the first letter of the abbreviation, with some English words indicate its function, said the presence of obstacles during the exchange, after discussion set the relevant parameters
Home was discussed, uniform use of the word naming their functions to observe can ensure better readability between, as well as members, since the use of micro-channel official development tools we use unified development tools, exchange them after unification there than before naming great progress.
Comment mainly to its function, by explaining its function in a more complex function section add comments.
V. test-related
Testers: Weijiang Feng, Zhang Beijing.
The main contents include tests to test different models of adaptation and the corresponding functions, including query with the topic, the topic of real-time recommendations, changes to individual labels and publishing topics functions.
1. participate in the test model as millet mix2s, glory v20, respectively MIUI11 relates to a system and EMUI10, are Android-based systems.
VI. Testing Tools
1. participate in the test model as millet mix2s, glory v20, respectively MIUI11 relates to a system and EMUI10, are Android-based systems.
VII. Test Evaluation
Testing is not a problem on both phones, but do not rule out the cause fewer models, the current mainstream manufacturers OPPO, vivo, oneplus, Meizu, were not tested, the future will end iOS relevant tests to ensure its availability.