Frog Frog Recommended: A little programmer work experience summarizes the ASP program development for more than two months, summarizes the experience in the development process and the indirect experience gained from others, combined with the actual work, just wrote. 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. At least 2 people should be tested before publishing; 3. Use the ALT and TITLE attributes to the link; 4. Set IMG Width and height properties; 5. Operations to the database generally include addition, delete, modify, query, pagination, listing, listing, listing; 6. Consider customer screen resolution and screen color; 7. Suitable for most low version browsing Consider the support of ActiveX, RDS, XML, DHTML, Java Applet; 8. Caches the input and output; 9. Reduce the access to the database: the result of the cache conversion; 10. Avoid failure and errors ; 11. Using Meta Tags:
station. As a pioneer and forerunner in the Internet industry, Kyushu Company, Hebei, adhering to the spirit of enterprising, innovation, has developed into a support
Have strong technical strength, energetic and competitive high-tech shares. "> 12. All forms input To do the necessary client authentication, and the server filtering the measures of SQL injection; 13. Website overall design style Unity; 14. There is a good overtime business process navigation; 15. Programmer write a good development instruction document:. Clear customer needs analysis. Page function assignment instructions. Program main function descriptions and functional analysis instructions. Database design instructions, Detailed to each table, each field, each stored procedure, view function and T-SQL statement. To customer write programs use help notes. Write the SQL execution statement of the main business process 16. All programs must be at least 3 different development degree version of the backup; 17. To have a good error handling function, you cannot provide users with a more detailed error description, but you have to clear the error. 18. Use the #include reusable code, all more Both the same code is packaged into a function; 19. # include file Do not use .inc suffix, use .asp or set .inc's application map; 20. Store the MDB file in the non-Web path, the database file name change Cheng .asp file, and in the name of the # character; 21. There must be reasonable indentation and appropriate comments in the program; 22. Specify the default parameters of the ADO call, avoid errors, accurately designate Command Type, and be good at using Recordset Field attribute; 13. Large program uses the SQLServer database, uses stored procedures; 14. Use server.transfer instead of server.Redirect; 15. Try to open the database as much as possible, try to turn off the database early; 16. Write copyright statement at the bottom, Protect intellectual property; 17. Consider replacing the session maintenance status with cookies, hidden form fields, queryString, etc.; 18. Good at using Application to cache content or frequently updated frequently or from time to time; 19. Use response.expires = -10000 in the right place Statements and response.buffer = true statements; 20. Do not store large arrays, record sets, and database connection instances in session or Application; 21. Reduce session.timeout, and script.timeout; 22. Close script debugging; 23. Good at Use client technology such as XML, XMLHTTP, JS, CSS, VML to share the server work; 24. Try to connect to the database provider using OLEDB; 25. Don't use SELECT *, write the fields; 26. Can use getString and Try to use the getRows method; 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 rushing
Time to do, indicating that you didn't make reasonable arrangements. Generally, it is the most important thing to focus on the most important thing.
The second is the most basic. Finally, it is otherwise, reasonable arrangements, often makes work more than half-effort; 28. Don't commit a second time, good at summarizing frequent, classic, easy to appear errors, Improve yourself
Habits, make it better, logic is more smooth, readable, more perfect; 29. Do some universal, reusable modules, build your own tutorhe book library and function library, placed in place, and To ensure that it is necessary to find it quickly; 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 best
I know what you have done. It is a very good idea to guide the work, this first needs you to divide the project into several individuals.
The completed small module, sometimes understand some common sense of software engineering, guide your work; 31. Time is the statement, the efficiency is higher than everything, you want to do every way to improve your work efficiency, of course, try to guarantee the quality and safety of works as much as possible
Under the premise; 32. More exercise, rest, more accompany your family and friends, communicate with people, these are almost the lack of programmers.
Some of this article refers to the "ant e-commerce" "how to write excellent ASP business applications?"
