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

What do I tell my manager?


Refactoring and then adding functionality can often be faster than simply adding the functionality while adding value to the existing code base. Many good managers, who properly understand software and how it is developed will understand this.

Of course there are managers who are clueless about what software actually is, they are often driven solely by deadlines and may be reluctant to learn more about their subject field. I am talking about the horror story developers I have mentioned earlier in this book. Sometimes, Scrum Masters are also guilty of this, due to the fact they may not be able to relate to the entire software development life cycle.

As Martin Fowler himself put it:

"Of course, many people say they are driven by quality but are more driven by schedule. In these cases I give my more controversial advice: Don't tell!"

Managers who don't properly understand technical processes may be intent on delivering on the basis of how rapidly software can be produced...