The document discusses best practices for working collaboratively using version control and IDEs. It recommends agreeing on a version control system like GIT or SVN and an IDE. It outlines a four step process for team environments: 1) developers set up local environments; 2) share code on a secure developer server; 3) test on a stakeholder server mimicking live; 4) deploy to the public live server. It also discusses following WordPress coding standards to maintain consistency across team members' code.

1. Making the jump to
GIT and IDE’s
(aka, playing nicely with others)

2. What are we
talking about?
talking about?
• Integrated Development Environments
• GIT and Subversion
• Working as a team
• Coding Standards

3. Who is this for?
• Intermediate developers;
• Team players;
• Public coding samples;

4. IDE’s
Making your job easier.

5. TextEdit is not an IDE

6. Example of an IDE

7. Common Features of
an IDE
• Code highlighting & variable identification
• Debugging
• Project Management
• Deployment Tools
• Function tips

8. Code highlighting

9. Debugging

10. Project Management

11. Function Helper

12. Function Helper

13. Deployment
• FTP
• Version Control Software

14. Version Control
Working in a team environment.

15. SVN
Subversive Tendencies.

16. Linux SVN

17. Visual SVN

18. Visual SVN with DIFF

19. GIT
A childish person with no manners.

21. SVN vs. GIT
Why choose one?

22. SVN vs. GIT
• GIT is localized, SVN is centralized;
• SVN only stores files, GIT stores file data;
• GIT is simply better;

23. Then why use SVN?
• SVN is what WordPress.org uses;
• SVN is what WordPress.com uses;
• SVN is old school, no reason to change;

24. Working in a team.
How to play well with others.

25. Working together
• Agree on a versioning control solution;
• Agree on an IDE preference;

26. Team Environments
Step One: Developers Workspace

27. Developers Workspace
• MAMP or LAMP setup as a local server;
• IDE,Versioning Control, and environments;

28. The Process (Step 1)
No.
Does it work?
Yes.

29. Team Environments
Step Two: The Team Workspace

30. the i in team.

31. Developers Server
• Secure working environment;
• Version control access only;
• Shares among developers;

32. The Process (Step 2)
No.
Does it work?
Yes.

33. Team Environments
Step Three: The Stakeholder Server

34. Developers Server
• Secure working environment;
• Version control access only;
• Shared among the stakeholders;
• Mimics the live server;

35. The Process (Step 3)
Are you happy?
Yes.

36. Team Environments
Step Four: The Live Server

37. Live Server
• Public environment;
• Version control access only;

38. The Process (Step 4)

39. The Process
Developer
Dev Server
Test Server
Live Server

40. Coding Standards
How to play well with others code.

41. Google the phrase:
WordPress
Coding
Standards

42. WP Coding Standards
• Single vs. Double Quotes
• Indenting and Formatting Code
• Brace Style & Spacing
• Semantic Coding
• Readability vs. Easy of Use
• General Best Practices

43. WP Coding Standards
• Single quotes are used when no variables
are present in the string;
• Double quotes process the contents;

44. 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”;

45. Formatting Code

46. Spacing Your Code

47. Capturing Errors

48. Semantic Naming

49. Standardizing