40 evidence that you are still a PHP rookie-you should learn the knowledge of PHP

You are a PHP rookie. if you: you will not use tools such as phpDoc to properly comment out your code and turn a blind eye to excellent integrated development environments such as ZendStudio or EclipsePDT. you have never used any form of version control system, for example, if Subclipse does not adopt certain encoding and naming standards or general conventions, it cannot be implemented during the project development cycle. if you are a PHP novice:

1. You will not use tools such as phpDoc to properly comment your code
2. Turning a blind eye to excellent integrated development environments such as Zend Studio or Eclipse PDT
3. Never used any form of version control system, such as Subclipse
4. Some coding and naming standards, as well as general conventions, cannot be implemented during the project development cycle.
5. Uniform development is not used
6. Do not convert (or) or verify some input or SQL query strings)
7. Do not thoroughly plan your program before coding
8. Test-driven development is not used
9. Coding and testing are not performed when an error is enabled (refer to the PHP function error_reporting)
10. Turn a blind eye to the benefits of the debugger
11. Do not refactor your code
12. Do not use MVC-like pattern to separate different layers of programs
13. Do not know these concepts: KISS, DRY, MVC, OOP, REST
14. Output (echo/print) content directly in your function or class instead of return.
15. Turning a blind eye to the advantages of unit testing or general testing
16. Always returns hardcoded HTML, but does not return pure data, strings, or objects.
17. Always hard-coded "messages" and "configuration parameters"
18. Optimizes SQL query statements
19. Do not use _ autoload)
20. Intelligent error handling is not allowed)
21. Replace $ _ GET with $ _ POST for destructive transfer operations.
22. I don't know how to use regular expressions.
23. I have never heard of SQL injection or XSS
24. Simple configuration is not allowed, and constructors of classes are not allowed to pass parameters and then execute the set/get method or constant definition during runtime.
25. Do not understand the advantages and disadvantages of object-oriented programming (OOP)
26. Abuse OOP regardless of the situation
27. Self-think that reusable software must be equal to/needs to make your code comply with OOP
28. Do not use smart default values
29. No single configuration file
30. I don't want to expose the file source code, but I replaced. php with the. inc suffix.
31. Do not use the database abstraction layer
32. You cannot keep the DRY style, that is, do not repeat yourself. if you are always copying and pasting something, it means you are poorly designed.
33. Without implementation, a function, class, or method can only do one thing and cannot be used together.
34. Failed to try the features of OOP, such as abstract classes, interfaces, polymorphism, inheritance, and access control modifiers (such as public, private, and protected)
35. Optimize your program system design without existing design patterns
36. You are not allowed to define basic directories when you have many files or directories.
37. Contaminated namespace, such as naming your library functions with common strings
38. No table prefix is used when database tables are used.
39. Do not use a unified template engine
40. Without paying attention to the existing PHP development framework, you are too lazy to explore. In fact, advanced development concepts and wonderful code are included.