How To Roll Your Own - PHP Antwerp meetup

As we mature as software developers, it becomes more and more important to increase the speed with which we are able to develop or applications. This can be done in a number of different ways, e.g. use a new IDE, use a new framework, pull in a specific package via composer, … .

In the last couple of years however, I have felt the need to take this concept one step further by creating a set of custom PHP packages that are perfectly in line with my own preferences and work flow. These packages have allowed me to significantly speed up the development of my projects by reducing the amount of repetitive actions and boiler plate code.

In this talk, I would like to give you a brief demonstration of the tools and techniques I have used to accomplish this and show you can do the same for your projects, be it Laravel, Symfony, Drupal or Wordpress. Additionally, I will highlight some of the lessons I learned over the last couple of years while taking this approach.

This slide deck is an updated version of my initial slides after some feedback from the community. It was used specifically for the PHP Antwerp meetup on 2016-07-27

Transcript

1. How To Roll Your Own Building your own development tools
2. www.ixudra.be - @ixudra
3. First website
4. Latest work
5. Lots of progress
7. Disclaimer
9. ixudra/curl
10. Why reinvent the wheel?
11. Why reinvent the wheel?
12. php-mod/curl
13. shuber/curl
14. ixudra/curl
15. ixudra/curl
16. ixudra/curl
17. * Data: 2016-07-27 Current stats*
18. ixudra.be/blog For further reading
19. In total
20. /ixudra/ixd-template • Custom project template • Preferred file and directory structure • Project config • Commonly used composer packages
22. Custom Laravel packages /ixudra/generators
23. Custom Laravel packages
24. /ixudra/portfolio
26. /ixudra/csi
27. In retrospect • Very time intensive but very much worth it. • Primarily for my personal work flow • Focus is on reusability
28. Other examples
29. Other examples
30. Other examples
31. Benefits • Huge gains in development speed • Increased consistency in all of my projects • New skills and and techniques can easily be transferred to other projects • Learned lots of new things in doing so
32. Benefits • Huge gains in development speed • Increased consistency in all of my projects • New skills and and techniques can easily be transferred to other projects • Learned lots of new things in doing so
33. Benefits • Huge gains in development speed • Increased consistency in all of my projects • New skills and and techniques can easily be transferred to other projects • Learned lots of new things in doing so
34. Benefits • Huge gains in development speed • Increased consistency in all of my projects • New skills and and techniques can easily be transferred to other projects • Learned lots of new things in doing so
35. Disadvantages • Being stuck in the same routines makes it more difficult to learn new things • More difficult to jump into a new project that doesn’t follow your workflow • Developing packages is hard • Very easily for packages to become obsolete
36. Disadvantages • Being stuck in the same routines makes it more difficult to learn new things • More difficult to jump into a new project that doesn’t follow your workflow • Developing packages is hard • Very easily for packages to become obsolete
37. Disadvantages • Being stuck in the same routines makes it more difficult to learn new things • More difficult to jump into a new project that doesn’t follow your workflow • Developing packages is hard • Very easily for packages to become obsolete
38. Disadvantages • Being stuck in the same routines makes it more difficult to learn new things • More difficult to jump into a new project that doesn’t follow your workflow • Developing packages is hard • Very easily for packages to become obsolete
39. How to start your own?
40. Time vs effort
41. Step one: check the competition
42. Step one: check the competition
43. Step one: check the competition
45. Step two: environment setup
46. Step three: research best practices
47. Step three: research best practices http://phppackagechecklist.com
48. Step four: implementation
49. Step five: documentation
50. Step six: set up reminders
51. Closing remarks • Call for action • Create one or more of your own packages and let me know how it all worked out • Take a look at my packages and tell me what you think • Rate this talk to help me improve my speaking abilities
52. Closing remarks • Call for action • Create one or more of your own packages and let me know how it all worked out • Take a look at my packages and tell me what you think (http://github.com/ixudra) • Rate this talk to help me improve my speaking abilities
53. Online course ixudra.teachable.com
54. www.ixudra.be - @ixudra Thank you all for listening http://github.com/ixudra