Comments are crucial. You won’t appreciate them until you leave your thousand-line script for a couple of days and return to and try and make sense of it. ﻿Anyone who can read code knows WHAT the code is doing. Explain ﻿WHY ﻿you've done it this way. ﻿

2. Write Useful Comments

Global variables and loops are a mess and can prove problematic when your application grows to millions of lines of code (which most do!). They may influence code elsewhere that is difficult to discern, or cause noisy naming clashes. Think twice before you pollute the global namespace with variables, functions, loops, etc. ﻿ALWAYS USE NAMESPACES.

3. Avoid Global Code

Never use names like <code>$k </code>, <code>$m </code>, and <code>$test </code>for your variables. How do expect to read such code in the future? Good code should be meaningful in terms of variable names, function/method names, and class names. Some good examples of meaningful names are: <code>$request </code>, <code>$dbResult </code>, and <code>$tempFile </code>(depending on your coding style guidelines these may use underscores, camelCase, or PascalCase).

4. Use Meaningful Names

Try to use tools like Ant or Phing to get your source prepared, compressed, and deployed. Building your whole application with a single command is a marvelous way to prevent errors and omissions that are inherent when performing repetitive tasks.

6. Use Automated Build Tools

For large applications spanning several classes and namespaces, you should have automatically generated API documentation. This is very useful and keeps the development team aware of “what’s what.” And if you work on several projects at the same time, you will find such documentation a blessing since you may forget about structures switching back and forth between projects.

7. Use Code Documenters

It's easy to overlook writing tests for a simple application, but as they grow in size it becomes increasingly important to be sure a change in one location after a time doesn't break something. Having tests makes sure the specific process you're testing always stays functional as intended.

8. Write tests

It’s easy to write bad, unorganized code, but it’s hard to maintain such code. Good code typically follows some standard for naming conventions, formatting, etc. Such standards are nice because they make things deterministic to those who read your code afterwards, including yourself. Use something like ﻿StyleCop ﻿to practice good habits.

1. Use a Coding Standard

Managing changes and revisions should be easy but effective, so pick whatever version control software that will work best with the workflow of your development team. I prefer using a distributed version control tool like Git or Mercurial; both are free software/open source and very powerful.

5. Use Version Control Software

Writing code can sometimes be the most difficult part of any software development process. In this article,we'll discuss 10 tips for better coding.

8. Write tests

Similar ideas to 8. Write tests

Making Checklists