1. Photos of the stand-up meeting on the day:
2. Project progress
Work done yesterday:
Further optimize the function and improve the server.
Work planned for tomorrow:
The server needs to be improved, and the back-end configuration needs to be modified.
Difficulties encountered at work:
The difficulty encountered today is that there is a problem with the framework set up by the server backend and needs to be modified.
3. Publish the project burndown chart
4. Code/document check-in record
code check in
5. Up-to-date (running) screenshots of appropriate project programs/modules
Code for the latest module
Screenshot of running result
6. Daily summary per person
Yang Zebin: Maybe I'm not good at the database aspect. There are always mistakes of this kind when building the framework. I try to modify it and hope for a good result
. Xiao Shisong:
Xie Qingyuan: In fact, developing a small program is like solving a logical problem. The first is to have an idea, that is, what the small program I wrote is going to do; then it is to think about one or more implementation methods for the core functions to be implemented, and choose one of them that I think is better; The next step is to divide the various major or minor functions involved into modules; the last step is to code and DEBUG into modules. In my opinion, except for the first step, the rest of the steps should be a cyclic process. During the coding process, you will always need to go back and modify the original module design, or even the initially chosen implementation algorithm.
Ye Wenning: After some preparations and sprints in the past two weeks, our applet has finally taken shape. Although there are still quite a few bugs, such as going to the server, the function is relatively simple. I was greatly encouraged, and Lin Weihang , who will continue to work hard in the later period :