In the world of PHP development, we often find ourselves facing the challenge of dealing with bloated, monolithic classes that hinder testability, extensibility, and maintainability. This talk aims to guide PHP developers through the process of overcoming the problem of unwieldy classes by employing effective structuring, refactoring techniques, and industry best practices.

2. Writing PHP code is easy! 👌

5. Not easy 🤔

6. legacy
legacy
legacy

7. 😭

8. The plan 📝

9. 1. Realize the problems
2. Understand what to do and how to do
3. Celebrate success 🍻

10. The problems 😬

11. Problems
- They do too much
God classes
- They hold too much
- Difficult to read, maintain and extend
- Responsibility is too wide
- Violates SRP

12. Problems
God classes

13. Problems
- They do too much
Long functions
- They hold too much
- Difficult to read, maintain and extend
- Responsibility is too wide
- Violates SRP

14. Problems
- Familiar parts of code in several places
Code duplication
- Need to apply the changes in several places
- Forged to apply somewhere - inconsistent system
- Leads to bugs

15. Problems
Code duplication

16. Problems
Code duplication

17. Problems
- No standards for a structure
Poor structure
- Difficulty in Understanding
- Maintenance Challenges
- Reinvent the wheel

18. Problems
- No documentation
Bad documentation
- Outdated documentation
- Difficult to understanding the system
- Onboarding Challenges
- Maintainability issues

19. Problems
- Difficult to understand
Lack of modularity
- Difficult to extend
- Difficult to maintain

21. BUGS

22. Software Development Costs: Bugfixing
https://blog.pdark.de/2012/07/21/software-development-costs-bugfixing/

23. What to do 🤔

24. No right way

25. Each team has its own practices

26. Our Superhero Approaches

27. 4. Make it platform 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. Follow Coding Standards

30. Which one?

31. 4. Copy Paste Detector (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. Understand responsibilities

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 to read
2. Easy to maintain
3. Easy to reuse
4. Easy to test
Benefits of focused components

35. Split by purpose
or type

36. - Entity
- Value Object
- Repository
- DTO
Most used types
- Validator
- Data Provider
- Mapper
- Service

37. Service

38. 4. Unaware of context
2. Stateless Operations
3. Сover one domain use-case
1. Domain-Focused Logic
Service

39. Wrong Service contract

40. Right Service contract

41. Platform-agnostic code

43. 1. Difficult to replace framework
2. Difficult to replace environment
3. Difficult to split by module
4. Code lives as long as framework
Problems

45. Apply Design Patterns

46. https://codeopinion.com/design-patterns-who-gives-a/
Patterns
usage

47. 4. Use proper naming
2. Think twice before use
3. Focus on commonly used patterns
1. Be careful!
5. Anti-Patterns
Patterns

48. Documentation

49. - Docs near the code
2. Docs as Code
- Docs under version control
1. Avoid meaningless PHPDocs
3. Document interaction with integrations
Documentation
4. Architecture Decision Record

51. Cover by tests

52. 4. Think as a 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 Coverage Report

56. Pros and Cons

57. 2. Easy to read 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. Success 🚀

60. Q & A