From: http://www.mpsky.com/infoview/Article_3486.htmlauthor: Blue Whale Date: January 26, 2005
Programs such as life, a person's code can see a person's personality, it is true. The program is art? Very like, is a code consisting of precision. In fact, anything is an art, as long as we excellence, everything is art. Art is always generated in harmony, opposing any hair. A good design, a good inspiration is always produced in a flat and beautiful environment. Imagine how bad the work is in a rush, the work mood is, you may think about it, come and complete the lives in these hands, and eat it early. The programmer is like this, and excellent programmers love their own code. They may see the code as a beating note, and there is a generous jitter. But others may be very lazy, they always find excuses, they are just programmers, do not understand art. Do you really understand art? ? ? In other environments, there is no art, such as today's evening, there will be many art masters. Turning the topic, I found that some beginners have a variety of questions when designing code: Question 1: The code is short, the east is a symbol, the West is a short sentence, like a cat, question 2: VB code case Regularization, although VB is not sensitive to the size, this problem occurs in the same code, the code is not beautiful; problem 3: Naming the variable is very grassroots; problem 4: Database design is very irregular, table name is XSTD, sp_gy, Field names XL, XS, etc. Database Design Talks: 1. Table Name Name Name Name Name Name Name Name Names, useful "_" to make a nomenclature in the previous database table, such as: Product_Detail, Student_information, Computer_Part_List, etc. However, I personally like to use the case where the case is written, I feel that it is more clear than using a lingering, such as ORDERDETAIL, Article, Userrole, Offethings, etc., must be clearly understood. Table names can be grouped, and is represented by a fixed term group, as StudentInformation StudentResult ForumMember ForumTopic ForumDetail Orders OrderDetail In addition, you can use "_" represents a design group table Account_User Account_UserRole Account_Permission Account_PermissionRole Article_ArticleChannel Article_Article Article_ArticleComment Article_RssChannel Article_RssSetting another table might encounter Complex nomenclature, such as Orders, Channels, Setttins, etc. I like to use the singlet, such as the USER is clearer than users. Database's field design database design generally requires a unique ID number as the primary key, such as the table of the main information, the summate of the detailed list requires the design ID number.
