Php beginner's standards

Php Cainiao standard 1. will not use tools such as phpDoc to properly comment your code? 2. do you turn a blind eye to excellent integrated development environments such as ZendStudio or EclipsePDT? 3. I have never used any form of version control systems, such as Subvision, CVS? 4. php Cainiao standards are not used

1. do not use tools such as phpDoc to properly comment your code?

2. do you turn a blind eye to excellent integrated development environments such as Zend Studio or Eclipse PDT?

3. I have never used any form of version control systems, such as Subvision, CVS?

4. do not adopt certain coding and naming standards, as well as general conventions, and cannot be implemented during the project development cycle?

5. do not use uniform development?

6. do not convert (or) or verify some input or SQL query strings?

7. do you plan your program not before coding?

8. do not use test-driven development?

9. Do I perform encoding and testing without enabling the error?

10. turn a blind eye to the benefits of the debugger?

11. don't refactor your code?

12. Do I not use MVC-like pattern to divide different layers of the program?

13. do not know these concepts: KISS, DRY, MVC, OOP, REST?

14. do you need to output (echo/print) content directly in your function or class instead of return?

15. ignore the advantages of unit test or general test?

16. always return hardcoded HTML, but do not return pure data, strings, or objects?

17. is it always hard-coded for "messages" and "configuration parameters?

18. are SQL query statements not optimized?

19. do not use _ autoload?

20. cannot I handle smart errors?

21. use $ _ GET instead of $ _ POST for destructive transfer operations?

22. I don't know how to use a regular expression?

23. Have you ever heard of SQL injection or cross-site scripting?

24. simple configuration is not allowed, and the constructor of the class is not allowed to accept parameter passing and then execute the set/get method or the constant definition during runtime?

25. do you not understand the advantages and disadvantages of object-oriented programming (OOP?

26. abuse of OOP regardless of the situation?

27. do you think that implementing reusable software must be equal to/must your code comply with OOP?

28. do not use smart default values?

29. Is there a single configuration file?

30. do not want to expose the file source code, but replace. php with the. inc suffix?

31. do not use the database abstraction layer?

32. do not keep the DRY style, that is, do not repeat yourself. if you are always copying and pasting something, it means that you are poorly designed?

33. I have not implemented one thing for a function, class, or method, nor can I combine them?

34. failed to try the advantages of OOP, such as abstract classes, interfaces, polymorphism, inheritance, and access control modifiers?

35. do not use existing design patterns to optimize your program system design?

36. do you not allow your users to define basic directories when you have many files or directories?

37. the namespace is contaminated, for example, naming your library functions with common strings?

38. Do I use a table prefix when using a database table?

39. do not use the unified template engine?

40. don't pay attention to the existing PHP development framework, so you are too lazy to explore. In fact, advanced development concepts and wonderful code are included.