Don't Repeat Yourself, Be Agile
0 likes467 views
The document discusses the importance of the DRY (Don't Repeat Yourself) principle in software development, particularly in relation to Drupal, emphasizing its implementation in Drupal 8 through object-oriented programming. It outlines perspectives from designers, developers, themers, and testers on applying DRY principles effectively, promoting the use of frameworks, automation, and package managers. The conclusion stresses the significance of reusing software components and automating processes for agile software development.
Don't Repeat Yourself, Be Agile
- 1. www.vardot.com Agile Jordan | January 2018 Don't Repeat Yourself (DRY), Be Agile
- 2. Agile Jordan | January 2018 Mohammed J. Razem CEO & Founder at Vardot m.razem@vardot.com @moerazem
- 3. Agile Jordan | January 2018 • Enterprise Open Source Products Built on Drupal • github.com/Vardot • drupal.org/Vardot
- 4. Our Clients
- 5. What’s DRY (Don’t Repeat Yourself) In Context
- 6. Agile Jordan | January 2018 Every piece of knowledge must have a single, unambiguous, authoritative representation in the system - Wikipedia (https://www.wikiwand.com/en/Don't_repeat_yourself)
- 7. Agile Jordan | January 2018 Don’t Repeat Yourself • One of the most important Programming Principles • Proper OOP is a direct application of DRY • Especially important in multi-tier architectures
- 8. Agile Jordan | January 2018 Don’t Repeat Yourself • Repetition is the root of all software evil • Duplication in logic should be eliminated via abstraction • Duplication in process should be eliminated via automation
- 9. What is Drupal? And Why as a Case Study? In Context
- 10. Agile Jordan | January 2018
- 11. Agile Jordan | January 2018 Drupal is… • Doesn’t have a good reputation • Drupal 5, 6, 7, was repeating it self • Not OOP • Doesn’t reuse popular software components
- 12. Agile Jordan | January 2018 Drupal 8 is Built on DRY • Drupal 8 uses OOP methodologies that implement DRY principle: i.e. Interfaces, Abstract Classes, Services, Service Containers …etc.
- 13. Agile Jordan | January 2018 Proudly Built Elsewhere
- 14. Agile Jordan | January 2018 Site Life Cycle Perspectives T E ST E R ( QA ) T H E M E RD E V E LO P E RD E S I G N E R
- 15. Agile Jordan | January 2018 Designer Perspective • Introduction of “front-end framework” is all about DRY - and Agile • Use Atomic Design • Consider Bootstrap, UI Kit, Material Design
- 16. Agile Jordan | January 2018 Designer Perspective DRY ✔ Not Applying DRY ✘ • Design atoms, molecules, organisms, templates, then pages • Design “canvas” or “pages” • Use Material Design or Bootstrap Extensions in Sketch to design • Design in Photoshop
- 17. Agile Jordan | January 2018 Designer Perspective • Consider: • Bootstrap, Material Design, or UI Kit • Atomic Design Principles: http://patternlab.io/ • Sketch not Photoshop
- 18. Agile Jordan | January 2018 Developer Perspective • Using Composer in your project • Build your distribution or package instead of starting from scratch every time • Using proper APIs, and entities for new system objects
- 19. Agile Jordan | January 2018 Developer Perspective DRY ✔ Not Applying DRY ✘ • Use Composer to include modules/components in your project • Commit contrib modules and components in your repository • Build a distribution or package for your own needs • Every time you have a new site, you download Drupal and other module/themes/libraries • Use proper Drupal 8 API. i.e. Services, Service containers, controllers, …etc. • Not using Drupal 8 API. Creating custom DB table with custom PHP code to write to it
- 20. Agile Jordan | January 2018 Developer Perspective • Consider: • Composer • Libraries in Drupal 8
- 21. Agile Jordan | January 2018 Themer Perspective • Use “Base themes”. i.e. Bootstrap • Theming for “View Modes” and global styling first • Use Libraries instead of custom inclusions • Using Less/Sass CSS to write CSS
- 22. Agile Jordan | January 2018 Themer Perspective DRY ✔ Not Applying DRY ✘ • Use Bootstrap as base theme • Build your custom theme from scratch • Theme view modes with consistent and global styling. Theme for general CSS classes • Theme fields. Theme specific classes. Each newly created view will need new theming • Use “Libraries” in Drupal to provide front-end specific functionality • Embed a custom JavaScript in your theme to provide front- end specific functionality
- 23. Agile Jordan | January 2018 Themer Perspective DRY ✔ Not Applying DRY ✘ • Use Less/Sass CSS variables, mixing, nested rules …etc. • Write regular (standard) CSS
- 24. Agile Jordan | January 2018 Themer Perspective • Consider: • Less/Sass vs CSS • Libraries in Drupal 8
- 25. Agile Jordan | January 2018 Tester (QA) Perspective • Testing is a process. Therefore, we need to automate the process • Using automated functional testing • Using Continuous Integration
- 26. Agile Jordan | January 2018 Tester (QA) Perspective DRY ✔ Not Applying DRY ✘ • Write an automated functional test and test by running it • Manually execute the test every time • Run a Continuous Integration build, that will run all automated tests • Everytime you release, test the whole system!!!
- 27. Agile Jordan | January 2018 Tester (QA) Perspective • Consider: • Behat tests • Continuous Integration build
- 28. Agile Jordan | January 2018
- 29. Agile Jordan | January 2018
- 30. Conclusion
- 31. Agile Jordan | January 2018 • Agile Software Development is tightly coupled with reusing software components • Spend more time researching working software than building your custom one • Automate processes: Automated testing • Use Front-end Frameworks and Package Managers
- 32. Agile Jordan | January 2018 Thank You!