1. Use PHP Core Functions and Classes
2. Create a Configuration File
3. Always Sanitize Data That Will Go into Your Database
4. Leave Error Reporting Turned On in Development Stage
5. Don’t Over-Comment Your Code
6. Keep Favorite Code Snippets Handy
7. Use a Good Source Editor to Save You Time
8. Use a MySQL Administration Tool (Like phpMyAdmin)
9. Use a PHP Framework
10. Connect with Other PHP Developers

For a full discussion of these points see the source.

Omo, that your number 9 is highly subjective.
I don't use framworks (out of choice)

And your number 10, you really need to tell them which kind of php developers you gotta roll with

spikes C: Omo, that your number 9 is highly subjective.
I don't use framworks (out of choice)

If you're going to be working with simple linear db queries, populating tables with iterations through a data set, getting and setting things, performing simple operations with the < > && || == != operators and you're going to be doing these things all by yourself with no future liklihood of expansion or collaboration... yes, procedural normal PHP is just good to go.

If however you're going to be performing complex operations in collaboration with other developers doing different things at the same time to reach one common goal, you'll need a framework... a uniform approach to getting things done so you don't have to read a developer's code wondering just what variation of weed the developer was on at the time of writing.

Using frameworks and going OOP are in my opinion highly arguable points in the industry but it really boils down to the task. It may be counter productive to use OOP or frameworks for hello-world-like web applications.

Dual Core:
If you're going to be working with simple linear db queries, populating tables with iterations through a data set, getting and setting things, performing simple operations with the < > && || == != operators and you're going to be doing these things all by yourself with no future liklihood of expansion or collaboration... yes, procedural normal PHP is just good to go.

If however you're going to be performing complex operations in collaboration with other developers doing different things at the same time to reach one common goal, you'll need a framework... a uniform approach to getting things done so you don't have to read a developer's code wondering just what variation of weed the developer was on at the time of writing.

Using frameworks and going OOP are in my opinion highly arguable points in the industry but it really boils down to the task. It may be counter productive to use OOP or frameworks for hello-world-like web applications.

I am not against OOP but against frameworks.
Yes, when you work with a team (especially when new), frameworks does the magic. But really, i can't sacrifice cleanliness and speed for such bloated stuffs.

I prefer learning the in's of a framework, then apply the knowledge in your own custom way.

Besides, it's not a must to use frameworks in group developments, you just need to appoint a good head supervisor and make sure the group works together. Most organisations have in-house developed frameworks

spikes C:
I prefer learning the in's of a framework, then apply the knowledge in your own custom way.

A framework is a predefined structure and pattern of getting stuff done optimizing time and productivity without sacrificing standards. Whether it is one of the many widely used ones or one developed by you, it is a framework.

Whether its a new team or a team made of of messi, iniesta and xavi... if these guys dont have a uniform structure of passing the codes around there will be avoidable chaos.

Dual Core:
A framework is a predefined structure and pattern of getting stuff done optimizing time and productivity without sacrificing standards. Whether it is one of the many widely used ones or one developed by you, it is a framework.

Whether its a new team or a team made of of messi, iniesta and xavi... if these guys dont have a uniform structure of passing the codes around there will be avoidable chaos.

I rest my case