Book Image

Mastering PHP Design Patterns

By : Junade Ali
Book Image

Mastering PHP Design Patterns

By: Junade Ali

Overview of this book

Design patterns are a clever way to solve common architectural issues that arise during software development. With an increase in demand for enhanced programming techniques and the versatile nature of PHP, a deep understanding of PHP design patterns is critical to achieve efficiency while coding. This comprehensive guide will show you how to achieve better organization structure over your code through learning common methodologies to solve architectural problems. You’ll also learn about the new functionalities that PHP 7 has to offer. Starting with a brief introduction to design patterns, you quickly dive deep into the three main architectural patterns: Creational, Behavioral, and Structural popularly known as the Gang of Four patterns. Over the course of the book, you will get a deep understanding of object creation mechanisms, advanced techniques that address issues concerned with linking objects together, and improved methods to access your code. You will also learn about Anti-Patterns and the best methodologies to adopt when building a PHP 7 application. With a concluding chapter on best practices, this book is a complete guide that will equip you to utilize design patterns in PHP 7 to achieve maximum productivity, ensuring an enhanced software development experience.
Table of Contents (14 chapters)
Mastering PHP Design Patterns
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Cart before the horse


Like most developers, I occasionally get bemused by some project management strategies; putting the cart before the horse is no exception.

Putting the cart before the horse is an anti-pattern under which features that never need to be built are architected, thus wasting time. The particular setting this annoys me is in technical meetings discussing a long-term technical plan where a project manager will discuss a feature and immediately demand the technical details of how this feature could be implemented.

Firstly, it's important to note that good developers should go away and have research time to come up with a solution. A developer is only made stronger by the ability to research their intended solution, to break out with their development team, to look online for other people facing similar issues, and then to come back with a unified, well-architected solution.

I spoke at the inaugural Lead Developer conference in London, and there was one quote that stood out to...