Posted on Monday 7 November 2005 - Popularity: unranked
If you’re already a PHP Programmer, I’m sure you already know about a lot of the mistakes outlined here, and if not have a look at it in order to become a better coder.
From part one:
- Improper use of printf
- Misapplying Semantics
- Lack of Inline Documentation
- Too many variables, too much time
- Rewriting existing PHP functions
- Not separating client side from server side
- Using Outdated Paradigms
From part two:
- Not Following Basic Naming Conventions
- Not Thinking Things Through: Databases & SQL
- Lack of Error Checking
- Overusing OO
- Misusing Regular Expressions
- Programming PHP Like It Was Some Other Language
- Not Being Security Conscious
From part three:
- Cut and Paste Coding: The Wrong Way
- Not Having Project Code Guidelines
- Not Doing a Code Review
- Hacking at Design Flaws
- Excluding the User from the Design Process
- Not Sticking to a Project Plan
- Getting Lost in Time
Of course a lot of those can be applied in similar form to other programming languages as well. Not that I think that there are many programmers that aren’t victims of some of those mistakes, myself included.










