PHP Industrialization
6 likes2,788 views
The document discusses the industrialization of PHP development, emphasizing the need for efficient coding practices, code refactoring, and the use of version control systems. It outlines a three-stage approach to scaling PHP applications, which includes conventions, frameworks, unit testing, and continuous integration. Additionally, it highlights the importance of documentation, agile methodologies, and collaboration in software development.
PHP Industrialization
- 1. PHP’s industrialization The new frontier
- 2. Agenda Scale up your work Get the tools and methods Go to the other sessions in Barcelona
- 3. Speaker Damien Seguy Expert Open Source services Raise elePHPants damien.seguy@alterway.fr
- 5. Function lists 692 defined functions, 611 actually used function CMP2() : 18 different definitions fct_create_thjipk(), datefren(), fct_lstagt_key(), phpinfo_system_old(), fct_repeat_even_requ(), fct_vrai_champ_general() Every one letter variable used : $a, $b, $c,...
- 6. Function spring cleaning It’s time to check them List them, see what they do Refactor the code, remove doubles Gather them in a central library, document them Build a solid framework...
- 7. Function spring cleaning It’s time to check them List them, see what they do Refactor the code, remove doubles Gather them in a central library, document them Build a solid framework...
- 8. Romantic PHP
- 9. Modern PHP
- 10. Reality check 65 portals next 6 months 6 people to upgrade 350 intranet 120 events sites a year on 150 servers App on one city, cover 12 cities by xmas, expand to 2 countries next year. full time employee for deployements
- 11. PHP industrialization Going from single to multiple Being proactive, rather than reactive Scale your work, not your server Otherwise, go to Rasmus session
- 13. Conventions PEAR, Zend Frameworks, Symfony... Choose one, use one Bring unity Code_sniffer
- 14. IDE Choose it for ease of use Netbean / Symfony, Zend tools, Komodo / cakePHP Code browser, editor, debugger, unit test integration, VCS integration, framework integration.
- 15. VCS Subversion, git, CVS, bazaar Resolve conflicts Stores and distribute the code Allow versioning, paralell development, rollback Code not in VCS does not exists
- 16. VCS Code Bug Track Production VCS Continuous Unit Test integration
- 17. Recommanded sessions Clean Code / Zend Framework
- 19. Methodologies Explain how you produce code Get your users involved Make short cycles to deliver, adapt and polish Agile methodologies : SCRUM, XP, Lean SD, Open Unified Process
- 20. Short cycles
- 21. Frameworks Frameworks Choose one, for development speed Components, conventions, scafolding, tests Community, expertise, training
- 22. Unit Tests PHP Unit, Simple Test, Lemon, Zend_Test, phpt
- 23. Tests helps decouple Production Avoid regression Code Platform Prevent your recall Shows progress Serves as manual Help at communication Customer use
- 24. Functional tests GreenPepper, Fitnesse
- 25. Recommanded sessions Agile development for PHP, SCRUM con exito Symfony 2.0 State of quality assurance tools
- 27. Automated deployment Phing, maven, ant, pear Needed for continuous integration The forgotten part of development Compulsory for large plat-forms, high scaling
- 28. Continuous integration Check the code in back ground phpUnderControl, Xinc, Hudson Graphs the results Compilation, code sniffer, unit tests, coverage Log, inclusion, performances... Share with the team
- 30. Conception Class diagram, database schema, navigation ArgoUML, StarUML, PowerArchitect Describe the general organisation List everything that will need name Class, methods, constants, SESSION, includes... Check the result
- 31. Conception Document things before hand Auto-generate phpdoc Check usage in the code, check undocumented
- 32. Documentation From developper to users Have developper start it Add comments Turn it into a wiki
- 33. Recommanded sessions Tallar de PHING Continuous integration
- 34. Even further? Continuous deployment (a la flickr) Cross auditing Collaborative auditing Static analysis
- 35. Most tools come from Java Hudson / Xinc Junit / PHPUnit CheckStyle / Code Sniffer UML to PHP (but not the reverse) Static audit analysis? Code navigation ? Code audit tool ? almost...
- 39. Documentation Level 0 : in code Level 1 : automated, manual PHPdoc, PHPdocumentor, Doxygen Level 2 : Wiki, blogues Level 3 : books, conferences
- 40. Scaling up coding Do more Leave part of it to others
- 41. Handling bugs Level 1 : manual test before production Level 2 : automate tests before production Level 3 : hand out tests to functional
- 42. Tools Firefox, Web Developper PHP Unit, Simple Tests, phpt, Push 2 Test GreenPepper, Fitnesse
- 43. More tests Get more tests Hand them to your users Use them in requirements Use them for docs
- 44. Team Conception à cycles courts Conventions de programmation Mantras de programmation Audits croisés
- 46. Progression Tests unitaires Tests fonctionnels Intégration continue Documentation automatique Suivi des conventions
- 47. Production Déploiement automatique Tests d’IHM Suivi des bugs
- 48. Avoid dead end tools Writing comments that are rarely read Producing doc ? Reusing unit tests ?
- 49. Scale up your work direct communication is OK for 2 mail is OK for 4 mantis is better
- 50. Aspects Automation API, PHPUnit, Including users in the tests Standards (SOAP/WSDL)
- 51. 3 phases of evolution Experimentation Mission critical Strategy
- 52. Approach of coding We’ll do what we need We’ll gather in the end to make this a good library This shows a lack of anticipation