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

Tests fight legacy


Automated tests are the best tool to fight legacy code.

By having automated tests such as unit tests or behavioral tests, you are able to refactor legacy code effectively with confidence that little can be broken.

Badly written systems often consist of tightly coupled functions. One change to a function in one class may well break a function in a completely different class, leading to a domino effect of more classes being broken until the entire application is broken.

In order to decouple classes and follow practices such as the Single Responsibility Principle, refactoring must be carried out. Any refactoring effort must be sure not to break code elsewhere in an application.

This brings us onto the topic of test coverage: is it a truly meaningful figure?

Alberto Savoia answered this question best in an amusing anecdote he placed online on artima.com; let's take a read:

Early one morning, a programmer asked the great master: "I am ready to write some unit tests. What code coverage...