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

You need to sack people sometimes


I have worked in development environments where managers are too scared to sack, they either just torture developers by punishing them for a job they evidently can't do by trying to put perverse restrictions on development teams or let them wreak havoc on the development processes.

Talented developers get disillusioned by the production of bad code or the unequal skill-basis. Other developers get away with poor code when they are often forced into a maintenance nightmare. Faced with the prospect of a maintenance nightmare (or in all likelihood, an increasing maintenance nightmare), they then resign.

Alternatively, the restrictive work conditions imposed to compensate for bad developers disillusion talented developers. Sick of being treated like idiots (because the other developers are idiots), they then take a job offer at a far better firm that offers them far better career prospects, and a better working environment with happier, more talented staff. They...