B-S-T Easy as 1-2-3: Best Practices, Standards & Tools Tips
1. B-S-T
easy as
1-2-3
Best Practices, Standards & Tools/Tips
to make your life simpler
Sunday, September 27, 2009
2. What’s the Point?
Good development is good, but
better development kicks ass.
If it can be done easier and better
with less effort - why not?
Sunday, September 27, 2009
4. Best Practices
A Best Practice is a technique, method, process, activity, incentive or reward
that is believed to be more effective at delivering a particular outcome than any
other technique, method, process, etc. The idea is that with proper processes,
checks, and testing, a desired outcome can be delivered with fewer problems
and unforeseen complications. Best practices can also be defined as the most
efficient (least amount of effort) and effective (best results) way of
accomplishing a task, based on repeatable procedures that have proven
themselves over time for large numbers of people.
Wikipedia: http://en.wikipedia.org/wiki/Best_practice
Sunday, September 27, 2009
6. Best Practices
(the best part)
By definition, best practices are what any group of developers and professionals
have decided work best for any given situation. This means they’re opinions
that have been confirmed by others, but it doesn’t mean that they’re law.
Any developer can suggest a new practice at any time. Every developer has
their own speciality. Find your niche and suggest away!
Sunday, September 27, 2009
7. Best Practices : What
- Not just about PHP. Think bigger.
- Best makes better
- Biggest bang for the buck
- Defining them is hard (no, really)
Sunday, September 27, 2009
8. Best Practices : Good
- Hit the ground running
- Helps you consider the important things
- Defines a set of “rules” you can use
- Keeps you current
Sunday, September 27, 2009
9. Best Practices : Bad
- Do more harm than good
- Understand! or don’t implement
- “Old wine in new bottles”
- Best? or Just Good Enough?
- Skip to the good parts
- Consider the future
Sunday, September 27, 2009
10. Best Practices : Consider
- How to benchmark the results
- Have the knowledge in-house
- Remember to innovate!
Sunday, September 27, 2009
11. Best Practices : PHP
- Unit testing - Source control
- Documentation - Well-structured
- Standardized Deployment - Integration tests
- Design patterns - Benchmarking
- Coding standards
Sunday, September 27, 2009
13. Standards
A technical standard is an established norm or requirement. It is usually a
formal document that establishes uniform engineering or technical criteria,
methods, processes and practices. A technical standard may be developed
privately or unilaterally, for example by a corporation, regulatory body, military,
etc. Standards can also be developed by groups such as trade unions, and trade
associations.
Wikipedia: http://en.wikipedia.org/wiki/Standards
Sunday, September 27, 2009
14. Standards : What
- Not just about PHP. Think bigger.
- Proven excellence
- Regularly used by a certain group or project
Sunday, September 27, 2009
15. Standards : What
- Naming conventions
- Variable definitions
- Commenting styles (like DocBlock)
- Use of external libraries
- How things fit together
Sunday, September 27, 2009
16. Standards : Good
- Levels the playing field
- Easier to get in on the game
- Can reduce the small issues
- Public standards make for easier integration
Sunday, September 27, 2009
17. Standards : Bad
- Where’s the quality control?
- Too strict?
- Could stifle creativity
- Poor implementation
Sunday, September 27, 2009
18. Standards : Consider
- Will it work for your group?
- Does the team size warrant the effort?
- Will the team accept it?
- Think wide, then narrow
Sunday, September 27, 2009
21. Tools & Tips
Tools you can use to help encourage, enforce, plan
out, etc.
Helpful hints and tips on their implementation
Sunday, September 27, 2009