Joomla DevelopmentSteven Pignataro – CEO/Partner ‘corePHP’
Intro
Quick Questions firstHow many here work as a team developing projects?
How many have used SVN or GIT?
How many of you are developers?
How many of you are experts?
How many of you would like to make more money by working faster?Coding StandardsWhat is a coding standards?
Have higher quality / improved standards of released products / web sites
Easier to maintain from developer to developerNaming ConventionsClasses:
Classes should be given descriptive names. Avoid using abbreviations where possible.
Separate each word with underscore.
We use underscores instead of Camel Case (like Joomla!)
Private Class members are preceded with _
Example: _init_tree()Function Definitions	This example is based on the K&R styleDescriptionsDescriptions are important as it helps other developers determine what is going on in the code itselfCoding Standards Example
Coding Standards TricksMake sure all coding is done with Maximum Error Reporting or E_STRICT
Make sure all your developers use the same patterns and have there IDE or favorite text editor setup properly to interpret the code.
Some example references:
http://pear.php.net/manual/en/standards.php
http://area51.phpbb.com/docs/30x/coding-guidelines.html
http://docs.joomla.org/Coding_style_and_standardsSVN vs GITSpeed
Handling of the repository
Size of repositories
Maturity of the repository
Ability to move to different versionsWhy use SVN or GIT?Ability to work with code with a team of developers
Copy of revision code
Apply immediate backups to a last known working revision
See who performed the update
Version control allows you to bring your new member up to speed with branches for testing instead of using actual live code to test.Which is betters?GIT of course!
You can use GIT off the grid – instead of being connected to the network

Joomla! Day Chicago 2011 Presentation - Steven Pignataro