@phpdeveloper.org
Matthew Weier O’Phinney & Mike Naberezny, did a great job on this session. The talk went very smoothly, each of the speakers traded off on presenting the various sections.
The session also dealt with other collaboration topics (commincation using IM, wiki etc) however I with the PHP/Development issues.
Source Documentation
- PHPDoc is the defacto documentation standard, it can be parsed by PHPDocumentor and Doxygen
- Use @category and @package to manage your documentation
- Using PHPDoc allows all developers to immediately understand your code
Unit Testing
- Focusing on PHPUnit
- Test religiously
- Without tests, code is fragile and will regress - there is nothing to tell you when you break your code.
- You are not wasting time by creating tests, you're wasting time by peppering your code with var_dump() and trying to debug code manually.
- Learning to write good object oriented code that is testable takes practice and discipline. Learn to design for usability.<o:p></o:p>
- Test-First methodology allows the tests to become the specification of code you are writing.<o:p></o:p>
- Using Classes is not Object Oriented Design
- Source control was on the benefits of using SVN to manage your code.
- Learn to use tagging and branching instead of committing everything to HEAD
- Trac is cool (I caught up on emails during this section - great wifi)
Deployment
- Never edit code on the server
- Check out tagged branches from your svc software
- Deploy to a staging server on your production server, test first then modify the symlink.
- Write acceptance and integration tests: http://manuals.rubyonrails.com/read/book/17)
- Monitor Health of Servers: http://www.plope.com/software/supervisor/
- Store schema of your database by committing the schema into your svc server - suggestion: http://www.mysqldiff.org/ and pre-commit hooks