Hindsight Conference of Technical Blogs

for last week's feature show, we "nice!" the team failed to show the results. After that I had a reflection, and the most important thing was that everyone (myself included) had no strong executive power, and the reason behind it was that the technology was weak. But this is not An excuse for the failure of Alpha Publishing. Now summarized as follows:

　　1. function is not fine-grained. Specifically, only the design project will appear in the login and registration interface, but the details of the inside (such as the number of attributes, names ) in their own implementation of the process of deviation. At the project integration stage, we found that the functions we did did not match well.

2. the standing meeting did not hold well. If the stand-up meeting is open every day to discuss yesterday's work and the work to be done today, as well as the code that can be submitted, I can only say that this is an ideal state. Take myself. As an example, the implementation of a function is not smooth sailing, and sometimes the mistakes in the program may take half a day to solve (I really do). Team members have their own things to be busy, and the technology is not very good, so everyone's progress is very slow, to ensure that every day to have a compiled code submission is really difficult, which also led to the very little communication, here I have to do self-review: not good to organize the team to complete the task. Imagine what an embarrassment it would be if everyone could not complete their respective tasks on a daily basis ( more specifically, they would not be able to do it), and then everyone gathered together to have a standing meeting every day. Because even if the meeting, we have no results, and then decorate the next task is futile.

3. poor technical base. Originally this is not a topic that can be discussed, but it is still necessary to talk about this issue specifically. For the problems encountered in the project, we will work together to solve, special preparation is a technical problem. But it just takes a long time to do it. Then for the implementation of the new features to find information, learning, and then the implementation of the Code. Technology almost never mind, but we are afraid that people do not pay attention to the project.

Said a series of excuses. Now talk about harvesting. Debugging the errors encountered in the project can really exercise people's perseverance and ability, debugging process is to use the technology in the project to trace the trace, understand its implementation process, so as to facilitate the improvement of technology. Then in the process of implementing the new function is to immediately learn the relevant knowledge, in the premise of understanding the code of others, and then integrate into their own code, the process is a bit slow. First of all I will ask teachers to achieve a function to use what technology, is probably a what process, and then go to the Internet to find and learn relevant information. It took me almost two days to debug an error (and no one was helping again) in the first two days, and finally found out that the configuration of the network permissions was missing from the configuration file. This problem is caused by the fact that there is no check on the code part that is self-confident. So write the program still have to use some methods, such as test-driven development, for each write good function unit test, this need to step by step. And then in the team coordination work is also very important, when the function assigned to each group member, feel the pressure is not so big. And the team members on some of the functions are also quite good, this really let me understand the importance of teamwork.

Summary: The revolution has not yet succeeded, comrades still need to work hard.

Hindsight Conference of Technical Blogs