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

Uneducated manager syndrome


Has your manager ever built a web app themselves? I find that this is a fairly important characteristic for a manager to have. The same way a junior doctor will report to a doctor who has been through the process of being a junior doctor themselves, or a teacher will report to a head teacher who themselves has been a teacher, a software developer should report to someone who has been through that process themselves.

Obviously, in small teams (for example, a small design house that does web development on the side), an engineering manager might not be strictly necessary. This works well where managers do understand the need to defer decisions to the programmers where necessary. However, as soon as things scale up, there needs to be structure.

Decisions such as who to hire, who to fire, how to address technical debt, which elements need most focus, and so on, need to be taken by developers; in addition to this, they sometimes mustn't be taken democratically because...