In this chapter we covered some fundamental anti-patterns for you to avoid; some were architectural, some were PHP-related, and others were at the management layer.
Fundamentally, anti-patterns result in technical debt. By technical debt, we are talking about code that is so hard to extend that it becomes harder to make changes to later on.
Here's a list of things I want you to do to fix this:
Plan before you start coding
Make comments, and add a comment where the purpose of your code isn't immediately apparent
Make sure your code has structure
Try to avoid putting too much code in one method
Use DocBlocking
Use common sense approaches to PHP
In this chapter, we have learned some common design issues that can lead to severe problems; these principles can help you prevent sizable issues later on. Writing code to scale is an important factor of design. At its core, this requires understanding the constraints. Using proper strategies for inter-process communication can help your service scale...