Talk delivered during Software Talks in Rzeszów and Wrocław More Domain-Driven Design related content at: https://domaincentric.net/

1. The Top 10 things
That any pro PHP developer should be doing
@Cakper

2. @PhpersPL

3. 1. Test

4. Don’t be
F5 kind-of-tester

5. Be lazy
in a good way

7. UI Tests
✓ Hard to debug
✓ Not efficient
✓ Easy to break
✓ Combinatorial explosion of tests

8. (a + b)! > a! + b!

9. Tools available in PHP
- PhpUnit
- PhpSpec
- Behat
- Mink
- Codeception

10. 10 minutes rule

11. 1 minute rule

12. Never trust
your suite

13. Validate
business value

14. Testing teaches
you how to design

15. 2. Design

16. Learn Design
Patterns

17. Gang of Four

18. Creational
- Abstract Factory
- Factory Method
- Builder Pattern

19. Structural
- Adapter
- Bridge
- Decorator
- Facade
- Proxy

20. Behavioral
- Command
- Mediator
- Observer
- State
- Strategy

21. Domain-Driven
Design

22. it’s about focusing on the domain
and letting it affect the software
very much
Jimmy Nilsson

24. Functional
programming

25. Design better
functions

26. 3. Practice

27. Practice does not make perfect.
Only perfect practice makes perfect.
Vince Lombardi

28. Deliberate practice

29. 10 000 hours

30. Dreyfus model of skill acquisition
1. Novice
2. Advanced Beginner
3. Competent
4. Proficient
5. Expert

31. Code Kata

32. Code Kata
- Time to improve your skills
- Focus on the process, not results
- Practice
- Repetition
- TDD

33. Code Kata
- Uninterrupted
- Challenging
- No pressure
- Mistakes are good
- Baby steps

34. Kata Ideas
- String Calculator
- Code Breaker
- Argument Parser
- Bowling Game
- Fizz Buzz

35. Code Retreat

36. Code Dojo

37. Code Club

38. 4. Reuse

39. PHP-FIG

40. PSR-0

41. PSR-4

42. Composer
& Packagist

44. Packages registered: 77 263
Versions available: 374 917
Packages installed: 1 325 712 827
(since 2012-04-13)

45. Satis

46. Toran Proxy

47. 5. Contribute

48. Why Contribute?
✓ Gain Experience
✓ Build Resume
✓ Give Back
✓ Be Recognised
✓ Fulfil Ambitions

49. GitHub

51. Blog

52. IRC

53. StackOverflow

54. Facebook Groups

55. Speak

56. Organise a Meetup

57. 6. Network

58. Conferences

59. Learn

60. Get Inspired

61. Meet People

62. Give Feedback
Always

63. Twitter

64. Direct access to
people and brands

67. 7. Tools

68. Tools are part of you

69. IDE

70. Learn how to use it
efficiently

72. But know what happens
under the hood!

73. Coding Standards

74. php-cs-fixer

75. Profiling
& Debugging

76. Xdebug

77. Phpdbg

78. Xhprof

79. Blackfire

80. Shell

81. Fish

84. Provisioning

85. Hosting

86. Digital Ocean

87. Heroku

88. 8. Continuity

89. Continuous
Integration

90. Code Reviews

91. Jenkins

92. Travis CI

93. Scrutinizer CI

94. Continuous
Deployment

95. Capistrano

96. Continuous
Delivery

97. Codeship

99. Continuous
Improvement

100. Always leave the campground
cleaner than you found it.
Boy Scout Rule

102. Continuous
Learning

103. 9. Learn

104. Invest in yourself!
Me

105. Read

106. Technical books
- Clean Code / The Clean Coder
- TDD by Example
- Growing Object-Oriented Software, Guided By Tests
- Domain-Driven Design
- Working Effectively with Legacy Code
- Agile Software Development PP&P

107. Management & Methodologies
- The Lean Startup
- Impact Mapping
- The Deadline
- Rework
- Getting Things Done

108. Psychological books
- Thinking Fast & Slow
- The Power of Habit
- Outliers
- The Kaizen Way

109. Study

110. Study Online
- Coursera/CanopyLab
- Open University
- MIT/Stanford Websites

111. 10. Team Player

112. Communication

113. Don’t be a d***
when reviewing code

114. Pair Programming

115. Synergy effect

116. 1 + 1 > 2

117. Question

118. Compromise

119. Deliver

120. Be Pragmatic

121. Recap

122. 1. Test

123. 2. Design

124. 3. Practice

125. 4. Reuse

126. 5. Contribute

127. 6. Network

128. 7. Tools

129. 8. Continuity

130. 9. Learn

131. 10. Team Player

132. Thanks!
@cakper