How to write php project experience-PHP Problem-php.cn

How to write php project experience

PHP project experience summary

1. Variables

It is best to put all variables Stored in an array, this can bring a lot of convenience in program development, especially when the program is large. The naming of variables should suit your own habits. Whether you use Pinyin or English, it should at least have a certain meaning so that it is suitable for memory. The naming of variables should be standardized as much as possible and should not conflict with keywords in PHP.

2. Functions

PHP comes with many functions, which brings a lot of convenience to the writing of our programs. Of course, in large programs we often have to define many functions ourselves, dozens or even hundreds. Of course, in a program that uses a class, it should not be called a function, but a method. Let’s not talk about the use of classes here. If there are too many functions, it will inevitably become confusing.

Is there any way to solve this problem?

You can refer to the above method of using variables. Similarly, we can also put all the function names we define in an array. In this way, we can directly check whether the function has repeated definitions in the array at any time during use. If you find a repeated phenomenon, you can change it immediately. Improved program writing speed. Another thing to pay attention to when using functions is global variables. Although this is a small problem, it cannot be ignored. At this time, see if the variable has been declared as a global variable in the function.

3. Comments on the program

The comments on the program are very important. Whether it is C or JAVA, the comments on the program can often reflect the Good programming style for programmers. Whether it is of great benefit to others or to yourself, of course we are talking about the development of large-scale projects here, and the spirit of teamwork is very important.

When your program is difficult for others to understand, how can you talk about the spirit of teamwork? Of course, it's a different matter if you develop this large-scale project alone, or you are pressed for time and don't have time to write comments. But generally speaking, this situation is rare. Unless it's really an emergency. A good programmer will definitely add comments to every program he writes, even if it is for himself.

4. What kind of text editing software should be used to write the source program

There are actually no certain rules, as long as you like it. I prefer PHPEDIT, maybe because I'm used to it, but now I feel like I don't feel like writing PHP without PHPEDIT. When I first learned PHP, I used NOTEPAD to write it, because the program is relatively simple. So just use NOTEPAD to cope with it. For programs with hundreds of lines, using NOTEPAD is obviously inappropriate. Using PHPEDIT will increase your work efficiency several times, even if you have never used it.

5. Database design

The design of the database is a very important point in the development of large-scale projects, and is related to the success or failure of the entire project development. I won’t go into details. Everyone can accumulate experience in their own practice and slowly understand it. In short, it is best to determine the database design from the beginning. Although you can change the designed database structure during the development process, this will greatly reduce the development efficiency of the entire project. Who would be willing to change the database structure from time to time?

6. Use of classes

The use of classes mainly enables the reuse of code to reduce project development time and programmer workload. many. As long as classes can be used, classes should be used as much as possible. Using classes should develop a good habit, so that you can be comfortable where classes are actually used. It can be said that a large PHP project is composed of classes. It’s better to experience it slowly by yourself.

In short, when developing large-scale PHP projects, you must budget your time. Be especially careful if the customer changes his mind midway, and the result will be in vain.