PHP Rookie Standard
1. Do not use tools such as PhpDoc to properly annotate your code?
2. Are you blind to an excellent integrated development environment such as Zend Studio or Eclipse PDT?
3. Have you never used any form of version control system, such as Subvision, CVS?
4. Does not adopt a coding and naming standard, and general conventions, can not be implemented in the project development cycle?
5. Do not use unified development method?
6. Do not convert (or) also do not validate certain input or SQL query strings?
7. Do not thoroughly plan your program before coding?
8. Do you not use test-driven development?
9. Do not encode and test in error-enabled state?
10. Blind eye to the benefits of the debugger?
11. Do not refactor your code?
12. Do not use a similar MVC pattern to separate the different levels of the program?
13. Don't know these concepts: KISS, DRY, MVC, OOP, REST?
14. Instead of return, you output (echo/print) content directly in your function or class?
15. Blind eye to the merits of unit testing or general testing?
16. Always return hard-coded HTML, but do not return pure data, strings, or objects?
17. Always hard-code "message" and "Configuration parameters"?
18. Do not optimize SQL query statements?
19. Do not use __autoload?
20. Do you not allow intelligent error handling?
21. Use $_get instead of $_post to do destructive transfer operations?
22. Don't know how to use regular expressions?
23. Never heard of SQL injection or cross-site scripting?
24. Do not allow easy configuration, and do not allow the class's constructor to accept parameter passing and then execute the Set/get method, or runtime constant definition?
25. Do you not understand the advantages and disadvantages of object-oriented programming (OOP)?
26. Misuse of OOP without regard to the size of the case?
27. Is it necessary to make your code conform to OOP for the purpose of realizing that the reusable software must be used?
28. Do not take advantage of smart default values?
29. No single configuration file?
30. Do not want to expose the file source code, but with the. inc suffix instead of. php?
31. Do not use the database abstraction layer?
32. Can not maintain dry style, that is, do not repeat themselves, if you are always copying and pasting something, that you are poorly designed?
33. No implementation allows a function/class/method to do only one thing, nor can it be combined to use them?
34. The ability to try OOP, such as abstract classes, interfaces, polymorphism, inheritance, access control modifiers?
35. Do you want to optimize your program system design without the existing design patterns?
36. Do you not allow your users to define the base directory when you have many files or directories?
37. Polluting namespaces, such as naming your library functions with common strings?
38. Do not use table prefixes when working with database tables?
39. Do not use the unified template engine?
40. Do not focus on the existing PHP development Framework, lazy to explore, in fact, the development of advanced ideas and beautiful code is contained therein.