Download as ZIP, PPTX
Uploaded byDamien Seguy
Epitech industrialisation 2012.key
The document outlines methods and tools for industrializing PHP development. It discusses releasing code ownership, capitalizing on work through conventions, IDEs, frameworks, version control systems (VCS), unit testing, documentation, and involving users. User involvement can occur through functional testing, bug tracking, and agile methodologies. The talk recommends continuous integration, deployment automation, capitalizing all project phases, and transitioning documentation into a wiki to further scale PHP work.
More Related Content
Similar to Epitech industrialisation 2012.key
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Epitech industrialisation 2012.key
- 1. PHP’s industrialisation Epitech 2012,Paris, France
- 2. Agenda Tame your developmentcycles Scale up your PHP work Get the tools and methods
- 3. Speaker Damien Seguy CTO at Bysoft China damien.seguy@gmail.com
- 4.
- 5.
- 6.
- 7. Reality check 65portals 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
- 8. Three mantra Release codeownership Capitalize your work Involve your users
- 9. ∆ Convention ∆IDE ∆ Conception ∆ Framework ∆ Deploiement ∆ VCS Capitalization Ownership ∆ Unit tests ∆ CI ∆ Docs ∆ Bug ∆ Methods Tracking ∆ Functional tests Involvment
- 10.
- 11. Release code ownership Lowbus factor Don’t be the only one Ugly code and hacks Write code like everyone else 50% of dev time is spend on production actions Don’t be in the path of operations
- 12. Release code ownership Haveothers run your work without you Don’t invest yourself in the code Make code accessible to someone else
- 13. Code conventions PEAR, Zend Frameworks, Symfony... Chooseone, use one Bring unity Code_sniffer
- 14. IDE Choose it forease of use Netbean / Symfony, Zend tools, Komodo / cakePHP Code browser, editor, debugger, unit test integration, VCS integration, framework integration.
- 16. Frameworks Choose one, fordevelopment speed Components, conventions, scaffolding, tests Community, expertise, training Build a business layer
- 17. VCS Subversion, git, CVS,bazaar Resolve conflicts Allow versioning, paralell development, rollback Stores and distribute the code Code not in VCS does not exists
- 18. VCS Development Unit Test Production VCS Continuous Bug Track integration
- 19.
- 20. Capitalization Accumulate allphases of project Capture information along the way Avoid dead ends Think of who will reuse this
- 21. Unit Tests PHPUnit, Simple Test, Lemon, Zend_Test, phpt
- 22. Tests helps decouple Production Avoid regression Code Platform Prevent your recall Shows progress Serves as manual Help at communication Customer use
- 23. Conception Class diagram, databaseschema, navigation Describe the general organisation List everything that will need name Class, methods, constants, SESSION, includes... Check the result in the code (BOUML) ArgoUML, StarUML, PowerArchitect
- 24. Automated deployment Phing, maven,ant, pear Needed for continuous integration The forgotten part of development Compulsory for large plat-forms, high scaling
- 25.
- 26. User involvment Avoid tunneleffect Don’t confront the tidal wave of requests bugs, changes, new, adaptation, acceleration Have users do part of the work
- 27. Bug tracker Mantis, Trac,Redline, Jira Connect it to VCS, deployment Gather feedback from users without direct contact Goes into changelog when deploying
- 28. Bug tracker Mantis, Trac,Redline, Jira Connect it to VCS, deployment Gather feedback from users without direct contact Goes into changelog when deploying
- 29. Functional testing Greenpepper, fitnesse Wiki base : easy on non-technical users Gather business data and use case Tests a priori, test live Developper will do the connection into the code
- 30.
- 31.
- 32.
- 33.
- 34.
- 36. Continuous integration Checkthe code in back ground phpUnderControl, Hudson, Maven, sonar, Xinc Graphs the results Compilation, code sniffer, unit tests, coverage Log, inclusion, performances... Share with the team, users
- 37. Methodologies Explain how youproduce code Get your users involved Make short cycles to deliver, adapt and polish Agile methodologies : SCRUM, XP, Lean SD, Open Unified Process Agile practices may be sufficient
- 38. Documentation From developper tousers Have developper start it Add comments Turn it into a wiki
- 39. Recommanded sessions Introduction auTDD Continuous integration of PHP projects Simulation Scrum avec prototypage papier XP-game
- 40. Even further? Continuousdeployment (a la flickr) Cross auditing Collaborative auditing Static analysis
- 41.