Xiong Bin
2005.3.2
1. Introduction to the previous development project
I have written some small programs before and have not been exposed to large projects. A larger program written is a web server that provides special services. It is a daemon program that works with a single process I / O multi-channel. It receives the "GET" request from the client, and the request is a set of characters or numbers, and an optional interference scheme is added later. The web server generates a PNG format verification code picture with the corresponding interference according to the client's request, and returns it to the client. The entire process complies with the HTTP 1.0 protocol.
2. The habit of developing past projects
l The "Software Development Flow Diagram" when developed, often does not know what to do next.
l There is no detailed design when developing, usually coding directly.
l There is no project schedule when developing, and the progress of our work cannot be arranged very well. Sometimes I want to do it when I want to stop, and I don't know when I can do my job.
l When encoding, I try to adopt some authoritative books, but there is still no complete unified coding rules. I have not introduced the rules that have not been introduced in some books, I only want to write it. In this way, there are many places that I can understand, and the readability of the code is very low.
l In the past, I used Subversion as a code control tool, but there were still many misunderstandings and unknown places in use. First, since it is independently developed, for the two major two-largest use "version control" and "collaboration" of Surversion, I just exposed some of "Version Control"; second, often in the program has not completed stage Function is only the frequent operation of the small place; third, I use Windows panel (TORTOISESVN) to operate, which is unskilled in the mode of work. In this way, the understanding of its working principle and some advanced ways cannot be well mastered, which is very short of a professional programmer.
There is no maintenance manual to write the project, and the maintenance work is useless.
