Original post address: http://blog.9cbs.net/onlytiancai/archive/2004/08/09/69178.aspx
Frog Frog Recommended: Summary of a little programs work experience
Do more than two months for ASP program development, summarize the experience in the development process and the indirect experience gained from others, combined with the actual work, just write it. Of course, it is impossible to list all useful experiences, but at least have some work guidance effect, pull the experience or your own personal experience, please reply to add, thank you
1. All super administrators initial accounts are admin, the initial password is www.21hb.com;
2. Test before publishing;
3. Use the ALT and TITLE attributes for the link;
4. Set the IMG's width and height properties;
5. The operation of the database generally includes adding, deleting, modifying, querying, paging, and listing several functions;
6. Consider the number of customer screen resolutions and screen colors;
7. Suitable for most low version browsers, consider their support status for ActiveX, RDS, XML, DHTML, Java Applet;
8. Cache input and output;
9. Reduce the access of the database: the result of the cache conversion;
10. Avoid linkages and errors;
11. Using Meta Tags:
12. All forms input To do the necessary client authentication, and the server is filtered with the measures of SQL injection;
13. The overall design style of the website should be unified;
14. There must be a good overtime business process navigation;
15. Programmer Write the development instructions document:. Clear customer needs analysis. Page function assignment instructions. Program main function descriptions and functional analysis instructions. Database design instructions, detail to each table, each field, each store , The function of the view and the T-SQL statement. Write the program to use the help instructions. Write the SQL execution statement of the main business process
16. All procedures must have at least 3 different development degree versions;
17. To have a good error handling function, you cannot provide users with too detailed error description, but you have to clear the reason for the error;
18. Use the #include reusable code, and all the same code to use the same code above is enacted into functions;
19. # include file Do not use .inc suffix, use .asp or set .inc application map; 20. Store the MDB file in a non-web path, the database file name is changed to the .asp file, and in front of the name Add # characters;
21. There must be reasonable indentation and appropriate annotations in the program;
22. Specify the default parameters of the ADO call, avoid error, accurately specify Command Type, and be good at using Recordset's field attribute;
13. Large programs use the SQLServer database to use the stored procedure;
14. Use Server.Transfer instead of Server.Redirect;
15. Try to open the database as night, try to close the database early;
16. Write copyright statements at the bottom to protect intellectual property rights;
17. Consider replacing the session maintenance status with cookies, hidden form fields, queryString, etc.;
18. Good at using Application to cache content updated frequently or from time to time;
19. Use the response.expires = -10000 statement and response.buffer = true statement in a suitable place;
20. Do not store large arrays, record sets, and database connection instances in Session or Application;
21. Reduce session.timeout, and script.timeout;
22. Turn off script debugging;
23. Good at using client technology such as XML, XMLHTTP, JS, CSS, VML to share the server;
24. Try to connect to the database using OLEDB database providers;
25. Don't use SELECT * to write the field;
26. You can use getString and getRows methods to use it as much as possible;
27. Work must have an article, don't think about it, design and arrange the workflow, and then check it carefully. If you have a bad place, you must have modified it. You can't make it, you should do it the best. It is better to change the mistake first with it to let customers find errors. If you are driving time to do, you don't have a reasonable arrangement of work. Generally, the focus is on the most important thing, followed by the most important, then the second is the most basic. Finally, other, reasonable arrangements often make the work more than half-effort;
28. The same mistakes don't make a second time, good at summarizing frequent, classic, easy to appear errors, to develop the habits of improving their previous procedures, making it better, logic is more smooth, readable, readability, The program is more perfect;
29. Do some universal, reusable modules, build your own tutorial book library and function library, put it in place, and ensure that it will find it when you need it;
30. Be sure to let others know your work, although communication is a very headache between a technician and the outside party, but you have to try your leadership know what you have done. It is a very good idea to guide the work. This first requires you to divide the project into several small modules that can be completed. Sometimes you know the common sense of software engineering, guide your work;
31. Time is the statement, efficiency is higher than everything, and try to make every means to improve your work efficiency, of course, under the premise of ensuring the quality and safety of works;
32. Multi-sports, more rest, more accompany your family and friends, and communicate more with people, these are almost missing all programmers.
