Introduction
Everyone has an opinion on coding practices, people always believe their standards are superior. However coding standards should be decided upon, not argued about. Here at Triangle solutions we too take take coding standards seriously. For us they enable an easier project build, letting the coders think about the code, and the project managers about the client.
This entry will serve two purposes. Firstly to act as a location for Triangle's own coding standards and releated tools. Secondly to form a community of likeminded individuals who take coding practices seriously and who want to comment and form a universal standard for PHP and related technologies. These being SQL, XHTML and CSS.
Coding Standards - Why are they so important?
To develop anything programatically is difficult enough, this is why all programmers must work in an organised and systematic way. It is not obvious but the coding style you employ plays an important role in achieving this goal.
The idea is very simple: consistent code is much easier to maintain.
So, here are several reasons why to use coding specifications:
- Multi-developer projects require coding standards. Your peer programmers have to understand the code you produce. A coding standard acts as the blueprint for all the team to decipher the code.
- Even if you develop alone it's advised to adhere to standards, because it really pays off when you revise your code after a time.
- Simplicity and clarity achieved by consistent coding saves you from common mistakes.
- Code becomes extensible and reusable. You don't have to worry if people working on your current application would understand some reusable feature recycled from the previous project.
- It just looks professional!
External Links
| 
