Making the jump to GIT and IDE’s

(aka, playing nicely with others)

What are wetalking about?

•Integrated Development Environments

•GIT and Subversion

•Working as a team

•Coding Standards

Who is this for?

•Intermediate developers;

•Team players;

•Public coding samples;

IDE’s

Making your job easier.

TextEdit is not an IDE

Example of an IDE

Common Features of an IDE

•Code highlighting & variable identification

•Debugging

•Project Management

•Deployment Tools

•Function tips

Code highlighting

Debugging

Project Management

Function Helper

Function Helper

Deployment

•FTP

•Version Control Software

Version Control

Working in a team environment.

SVN

Subversive Tendencies.

Linux SVN

Visual SVN

Visual SVN with DIFF

GIT

A childish person with no manners.

SVN vs. GIT

Why choose one?

SVN vs. GIT

•GIT is localized, SVN is centralized;

•SVN only stores files, GIT stores file data;

•GIT is simply better;

Then why use SVN?

•SVN is what WordPress.org uses;

•SVN is what WordPress.com uses;

•SVN is old school, no reason to change;

Working in a team.

How to play well with others.

Working together

•Agree on a versioning control solution;

•Agree on an IDE preference;

Team Environments

Step One: Developers Workspace

Developers Workspace

•MAMP or LAMP setup as a local server;

•IDE, Versioning Control, and environments;

The Process (Step 1)

Does it work?

No.

Yes.

Team Environments

Step Two: The Team Workspace

the i in team.

Developers Server

•Secure working environment;

•Version control access only;

•Shares among developers;

The Process (Step 2)

Does it work?

No.

Yes.

Team Environments

Step Three: The Stakeholder Server

Developers Server

•Secure working environment;

•Version control access only;

•Shared among the stakeholders;

•Mimics the live server;

The Process (Step 3)

Are you happy?

Yes.

Team Environments

Step Four: The Live Server

Live Server

•Public environment;

•Version control access only;

The Process (Step 4)

The Process Developer

Dev Server

Test Server

Live Server

Coding Standards

How to play well with others code.

Google the phrase:

WordPressCoding

Standards

WP Coding Standards

•Single vs. Double Quotes

•Indenting and Formatting Code

•Brace Style & Spacing

•Semantic Coding

•Readability vs. Easy of Use

•General Best Practices

WP Coding Standards

•Single quotes are used when no variables are present in the string;

•Double quotes process the contents;

WP Coding Standards

•Single quotes are used when no variables are present in the string;

$x = ‘Hello’.$name;

•Double quotes process the contents;

$x = “Hello $name”;

Formatting Code

Spacing Your Code

Capturing Errors

Semantic Naming

Standardizing