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

YAGNI and defering decisions


You aren't going to need it – you don't need to add functionality until it's necessary. Only add things that are vital to the success of your project. You probably won't need a lot of functionality for the first version of your web app; it's best to defer this until necessary.

By deferring unnecessary functionality, you are able to keep your software design as simple as it needs to be. This helps you cope with the pace of change. Later in the software development process you will be more educated regarding the requirements, and more importantly, your client will have a more precise projection as to where they want the product to head.

When you make decisions on software later, you have more data and more education. Some decisions have to be made upfront, but if you can defer them, that's often a good idea.