Management of PHP development teams

Clarification: This article is excerpted from "talking about PHP Development Team governance and programmer Title". For the full text, click here to visit. After reading the title, many programmers may dislike it and say, "you don't need to talk about the title of a programmer. if you come up with this title, then you

Clarification: This article is excerpted from "talking about PHP Development Team governance and programmer Title". For the full text, click here to visit.

After reading the title, many programmers may dislike it and say, "you don't need to talk about the title of a programmer. if you want to come up with this title, do you have a title !"

I personally do not refute this statement. everyone has their own principles of being a person. As the saying goes, "I do not agree with your thoughts, but I do my best to defend your thoughts ". Yes, you can say that in your personal attitude. But what if I stand on the attitude of a team? Everything is gone!

Whether it's the marathon principle or the barrel principle, Westerners are indeed worthy of praise. But I think it is still lacking! As a complete team, it is necessary to have a few outstanding technical talents. A skill team must have a way of skill. otherwise, programmers who grasp money and development cannot grasp his mind! Therefore, it is necessary and necessary for Westerners to put their things in politics or to put them down in an environment where R & D is necessary. However, in the skill team, it is not optimal.

It is essential to lead an accurate skill direction for the development and strength of all teams. Now that we are talking about PHP today, let's say a few more things about PHP.

First of all, we need to standardize everyone's coding habits and adopt "tailism!

We recommend that you use the database classes of ADODB at the database layer to minimize the possibility of programmers writing SQL statements directly. This will benefit database transplantation and security in the future. The most important thing is to regulate everyone's writing habits. Although many people complain about the efficiency is not very good, but the author always thinks that a firm is higher than the efficiency, the individual must obey the group. If you still complain about the efficiency title, add a CPU and replace it with 2 GB memory. I don't know what the blame is. isn't the code written by ADODB faster than adding a CPU?

We recommend that you use MYSQL for the database! The minimum version is 4.1 or later. It is very necessary to support transactions.

There are many reasons for using MYSQL. First: good compatibility; second: relatively complete efficacy; third: easy configuration; fourth: support for open source. MYSQL5, which is not mentioned here. Since the development of programmers in China is still dominated by MYSQL4 PHP4, I do not want to cause incompatibility of development results to the team.

Apache is my decisive choice. I have learned from the 62% occupation rate in the international market: security, and the outstanding features of efficiency are undoubtedly beyond the reach of IIS. Although WINDOWS2003 SERVER has recently seized some market share, it is still difficult to shake Apache's position. There is also a more important role in the middle, that is, LIUNX. LIUNX is not discussed here, but as a good PHP programmer, if he doesn't know LIUNX at all, it is also boring. I can talk about it with my own situation: a few years ago, I developed a LIUNX virtual host management software. after receiving the requirement, I made a feasibility analysis of the skill plan, the invention involves a large number of control over the MYSQL database and APACHE. how can we achieve these control? In this case, you must have a certain understanding of the LIUNX system. Otherwise, the project is basically unavailable! Of course, there are many examples, such as the PHP server load balancer solution plan and the database dual backup plan ...... Too many.