Download as PDF, PPTX
Uploaded byFwdays
"PHP Code Avengers: Structuring, Refactoring, and Superhero Practices", Vladyslav Sikailo
The document discusses common challenges in PHP coding, particularly with legacy code and 'god classes,' which contain excessive responsibilities, making maintenance and readability difficult. It provides a comprehensive plan to address these issues through coding standards, documentation, design patterns, and testing while emphasizing the importance of coherence and modularity in development. Ultimately, the goal is to improve software quality and reduce long-term bug fixing costs.
More Related Content
Similar to "PHP Code Avengers: Structuring, Refactoring, and Superhero Practices", Vladyslav Sikailo
"PHP Code Avengers: Structuring, Refactoring, and Superhero Practices", Vladyslav Sikailo
- 2. Writing PHP codeis easy! 👌
- 5.
- 6.
- 7.
- 8.
- 9. 1. Realize theproblems 2. Understand what to do and how to do 3. Celebrate success 🍻
- 10.
- 11. Problems - They dotoo much God classes - They hold too much - Difficult to read, maintain and extend - Responsibility is too wide - Violates SRP
- 12.
- 13. Problems - They dotoo much Long functions - They hold too much - Difficult to read, maintain and extend - Responsibility is too wide - Violates SRP
- 14. Problems - Familiar partsof code in several places Code duplication - Need to apply the changes in several places - Forged to apply somewhere - inconsistent system - Leads to bugs
- 15.
- 16.
- 17. Problems - No standardsfor a structure Poor structure - Difficulty in Understanding - Maintenance Challenges - Reinvent the wheel
- 18. Problems - No documentation Baddocumentation - Outdated documentation - Difficult to understanding the system - Onboarding Challenges - Maintainability issues
- 19. Problems - Difficult tounderstand Lack of modularity - Difficult to extend - Difficult to maintain
- 21.
- 22. Software Development Costs:Bugfixing https://blog.pdark.de/2012/07/21/software-development-costs-bugfixing/
- 23.
- 24.
- 25. Each team hasits own practices
- 26.
- 27. 4. Make itplatform agnostic 2. Understand responsibilities 3. Split by purpose 6. Documentation 1. Follow Coding Standards 5. Apply Design Patterns List of approaches 7. Cover it by Tests
- 29.
- 30.
- 31. 4. Copy PasteDetector (phpcpd) 2. PSR-1, PSR-2, PSR-12 3. PHPStan, Psalm 6. CI/CD is a must 1. PHP Code Style (phpcs) 5. PHP Mess Detector (phpmd) Must use 7. Rector, PHP CS Fixer 8. …
- 32.
- 33. 4. Low coupling,high cohesion! 2. What is the role of the class? 3. KISS 💋 (and focused) 1. What does the class do? Think about
- 34. 1. Easy toread 2. Easy to maintain 3. Easy to reuse 4. Easy to test Benefits of focused components
- 35.
- 36. - Entity - ValueObject - Repository - DTO Most used types - Validator - Data Provider - Mapper - Service
- 37.
- 38. 4. Unaware ofcontext 2. Stateless Operations 3. Сover one domain use-case 1. Domain-Focused Logic Service
- 39.
- 40.
- 41.
- 43. 1. Difficult toreplace framework 2. Difficult to replace environment 3. Difficult to split by module 4. Code lives as long as framework Problems
- 45.
- 46.
- 47. 4. Use propernaming 2. Think twice before use 3. Focus on commonly used patterns 1. Be careful! 5. Anti-Patterns Patterns
- 48.
- 49. - Docs nearthe code 2. Docs as Code - Docs under version control 1. Avoid meaningless PHPDocs 3. Document interaction with integrations Documentation 4. Architecture Decision Record
- 51.
- 52. 4. Think asa test 2. Tests are the part of documentation 3. Safe refactoring 1. Early find problems Tests
- 53. Software Development Costs:Bugfixing https://blog.pdark.de/2012/07/21/software-development-costs-bugfixing/
- 54. 2. Component tests 3.Integration tests 1. Unit tests Commonly used tests types
- 55. Cubertura Test CoverageReport
- 56.
- 57. 2. Easy toread and understand 3. Reduced Bugs and Errors 1. Maintainability 4. Scalability Pros
- 58. 2. Learning 3. Over-Engineering 1.Initial Overhead 4. Initial Investment in Tooling Cons
- 59.
- 60.