It turns out that code and text are not available. Writing a little text is also normal when you write a product document, and it is normal. But when you really start writing code, even if you have a writing of the idea, you will never knock a few hundred lines of code, there will be an idea of playing with the keyboard.
I am an extremely no time concept. After writing the system analysis, I spent a few weeks in the leisurely, I just wrote a little program on the weekend, but I just want to stop, I still have to watch TV, listen Listen to music, play games ...
When I went on the last weekend of May, I started to be nervous. At that time, I had a 30% function in the past three weeks before June 12. The two weeks of time must not only write, but also to complete a simple test, release, these lives look trivial, but actually cost time.
However, I found out that there are some problems in estimating project progress in accordance with functional points. Although I only completed the function of about 30%, I have already completed the architecture and technical point of the system. In other words, there is no technical difficulty in the road after I will be in the road. And as I mastered with C #, the development schedule is much better than before. So, I think that when I estimate the project progress, I should not ignore the impact of technical difficulties, and the programmer's skills are a dynamic process. We should not see a person's development efficiency as a fixed value. Skilled, physical condition, and even mood have great impact on development efficiency, and can even reach multiple relationships.
The next two-week purgatory trip is more smooth. Since the company is more, I have not used it if I compress my sleep time. But sleep time and work efficiency are great. In the case of brain fatigue, logical thinking is easily confusing, and the chaos of programmer logical thinking, oh, or unclear, give software may be deadly defects. So I agree with the views in XP. I only worked for 40 hours a week. I even think that if the programmer should not exceed 30 hours per week, unless it is the last week. If you set a reach yourself, you will think just a week. After a week, we can enjoy the holiday, give the customer demo, temporarily bid to boring code life, so everyone will put a lot of things, increase productivity to one High degree. But if it is not enough for a week, the strike from programmers is from both physiological and psychological.
The sprint in front of program development is very similar to the charge in the war. If the first charge, all soldiers will play the best state, one drum to tear the other side's defense, but if a charge fails, then, will then decline, Three strokes. Therefore, the timing of the project manager chooses the charge, sometimes, the success or failure of a project may be the difference.
The entire program is satisfied, because I have used product design around the time, and many logical issues are clear at that time. The entire architecture is sturdy and elastic in the later development process, I believe that if you add or modify some functions, our changes will be small. The biggest advantage of logical code and interface is that the duplicate code is reduced, and it is easy to understand. The only thing is trouble is that because I don't use a unit test, in order to complete a function, I may want to modify three classes - interfaces, logic, service calls, or database operations.
What makes me dissatisfied is that the definition of the Web Service interface is not good. Because I define a lot of similar, in accordance with the needs of the program, if I want to get a set of data, there is an interface to return DataSet , And I need to get one of them, then another interface is needed. This is a little unsatisfactory. In addition, it is safe. I put the password directly to the database, which is extremely dangerous; and the user's verification is just playing in the login, and when calling the Web Service method, do not verify The legality of the caller, which is also extremely dangerous in the wireless environment, anyone can call your Web Service through the wireless device, get some data, or modify the data. For security considerations, it is the focus of the next phase.
Within the scope of the power, I still have some known attack methods, such as SQL injection, I have used my own way, once the possible SQL injection attack, the Web Service will throw an exception.
It is said that it is worth the exaggerated place. The most appreciation is the style of the interface. It is the lowest. There is also a multi-line display ListView control, which I have already impected it very much, and this time I finally realized the third party code.
The experience of this development is so much, this time I am a person from product definition, design, encoding, database, test, and release it all the way. Many places are done according to their own ideas. The effect is not bad. Some places have also surprised their childish, but the happiness after the bite is coming over, but everything is almost demonstrated.
Anyway, I have to give yourself a holiday. Just now DearBook sent "agile software development", huh, huh, it can finally relax.
