Of the 40 common bad habits of PHP programmers how many have you got？

2021-08-03 09:49:30
OfStack
 
Don't write comments 

Do not use IDE tools that can improve production efficiency 

Do not use version control 

Do not write code according to programming specifications 

Do not use the method of unification 1 

Don't think and plan before coding 

Do not perform coding and security detection before executing sql 

Do not use test-driven development 

Do not turn on automatic error reporting when coding (error_reporting) 

Do not use a good debugging tool 

Do not refactor your code (refactor) 

Do not adopt the hierarchical structure such as MVC 

I don't know the following concepts: KISS, DRY, MVC, OOP, REST 

Output something directly with print or echo in a function or class instead of returning it (return) 

Do not use or understand unit tests 

Returns HTMl instead of data, strings, objects, etc 

Bad code and configuration parameters (hard code messages and configuration parameters) 

Do not optimize sql queries 

Do not use __autoload 

Automatic error operation is not supported (it should be intelligent error correction) 

Use $_GET instead of $_POST for dangerous parameter passing (remember these 40 things are all wrong) 

Don't know how to use regular expressions 

I have never heard of sql injection and cross-site scripting (in terms of security, I should know the English of these two things: sql injection, cross-site scripting) 

Do not support simple configuration, pass parameters to class constructors, set/get methods, define constants 

Can't understand the advantages and disadvantages of OOP 

Use OOP no matter how small the thing is 

It is considered that reusable software is OOP 

Do not use the default value (don 't choose intelligent defaults) 

Do not use a single 1 profile 

Replace. php with. inc instead of letting others see the code 

Do not use the database abstraction layer (persistence layer) 

DRY (Dont repeat yourself) at development time. (That is, something that is always repeated in development) 

Do not develop reusable classes or methods 

Do not use abstract classes or interface classes, inheritance, polymorphism and encapsulation. 

Optimize your program without using existing design patterns. 

The user is not allowed to define the basic directory (this seems that PHP is not suitable, after all, it is not based on the operating system) 

Wrong use of namespace, using commonly used words as prefixes. (This will cause conflicts when others use it later. For example, define one function called array_push ()) 

Do not use table prefixes when using databases (this is important...) 

Do not use or use a strange template engine (it is convenient for team development, and everyone should use common templates) 

Don't look at the framework of PHP (most frameworks contain excellent code and advanced concepts. It is worth learning) 
 
Almost all the entries of this site are in, and if you have less than 30 entries, don't leave a message to stimulate me ~