1. Do not discuss whether ASP is outdated. What matters is not whether you use advanced technologies, but whether your design ideas are advanced;
2. the versatility of the project should be taken into account during design, and never do things without promotion value;
3.ProgramThe design should be concise, and the process orientation should be good enough, which is far better than the poor object-oriented design;
4. Theories serve practice, so do not be bound by theories (especially design patterns;
5. When the division of labor is reasonable, as few people as possible can form a project team, the communication overhead is too large;
6. There is no need for constant expansion. You need to leave enough space for your program and consider ways to minimize the workload and difficulty during system transplantation;
7. Do not ignore the interface design. In many cases, this is the only criterion for your project evaluation;
8. Write down your variable usage in regular documents. As the system increases, the debug cost will almost multiply;
9. Machine-generatedCodeDon't write your hand. The most precious thing is time;
10. Select the database or Oracle!
I thought I would study Java later, and the result was forced to study ASP.
I feel a little lonely since I went to 503 to study Java in a group, but now I am in 605 alone, and I cannot even see my teammates who have grown together.
The layout of 605 remains unchanged. The classroom is still the classroom, but the team here is no longer the seventh group, but the economic marketing department.
The only thing that remains unchanged is me ~~~