PHProokie, if you: 1. Not using tools like phpDoc to properly comment your code

2. Turn 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. Without adopting certain coding and naming standards, as well as common conventions, they cannot be implemented throughout the project development cycle.

5. Not using a unified development approach

6. Not converting (or) not validating certain input or SQL query strings (Annotation: refer to PHP related functions)

7. Not planning your program thoroughly before coding

8. Not using test-driven development

9. Do not code and test with errors enabled (Translation: refer to PHP function error_reporting)

10. Turning a blind eye to the benefits of a debugger

11. Not refactoring your code

12. Do not use MVC-like patterns to separate different levels of the program

13. Don’tknowthese concepts: KISS, DRY, MVC, OOP, REST

14. Instead of returning, directly output (echo/print) content in your function or class

15. Turning a blind eye to the advantages of unit or generic testing

16. Always returns hardcoded HTML, but never pure data, strings, or objects

17. Always hardcode “message” and “configuration parameters”

18. Not optimizing SQL query statements

19. Do not use __autoload (Annotation: refer to the relevant description in the PHP manual)

20. Intelligent error handling is not allowed (Translation: refer to PEAR’s ErrorStack)

21. Use $_GET instead of $_POST for destructive transfer operations

22. Don’t know how to use regular expressions

23. Never heard of SQL injection or cross-site scripting

24. Simple configuration is not allowed, and the constructor of a class is not allowed to accept parameter transfer and then execute the set/get method, or constant definition at runtime.

25. Not understanding the advantages and disadvantages of object-oriented programming (OOP)

26. Abuse OOP regardless of the size of the situation

27. Thinking that implementing reusable software must equal/need to make your code follow OOP

28. Not leveraging smart defaults

29. No single configuration file

30. I don’t want to expose the source code of the file, but use the .inc suffix instead of .php

31. Not using a database abstraction layer

32. You cannot maintain a DRY style, that is, do not repeat yourself. If you are always copying and pasting something, it means that your design is poor.

33. There is no implementation that allows a function/class/method to do only one thing, nor can they be used in combination

34. Failed to try OOP’s specialties, such as abstract classes, interfaces, polymorphism, inheritance, and access control modifiers (Annotation: such as public, private, protected)

35. Optimize your program architecture design without using existing design patterns

36. Don’t allow your users to define base directories if you have many files or directories

37. Pollution of the namespace, such as naming your library functions with common strings

38. Do not use table prefix when using database tables

39. Not using a unified template engine

40. Don’t pay attention to the existing PHP development framework and are too lazy to explore; in fact, advanced development concepts and wonderful code are contained in it.