Category: OOP

• Complexity
• OOP
• Programming

Imagine you’re having a great day at the office, you’ve got a brand new feature the customer is dying to have, and you’ve completed it in record time. You’re all ready to get it merged and peer reviewed. So you commit it, and push it to your build pipeline, where it’s analyzed. The build fails. Your analytics tool tells you complexity is too high! You’re given a numeric complexity value for your code, and a lower complexity value that you need to get your code’s complexity under.

• OOP
• CRC

Yesterday I had fun breaking down a complex system into simpler classes using CRC Models. CRC Models are Class Responsibility Collaborator models, and it allows you to identify classes that aren’t quite doing what they should be. Typically a key instance of when this practice is useful is if a system is consistently described as confusing, or people keep questioning if thing X should really live there. These phrases are symptomatic of a poor object class name/responsibility/collaborator match.

• OOP
• Development
• PHP
• SOLID
• OOP

How to use the Dependency Inversion Principle in PHP. The fifth in a series on SOLID

• Development
• PHP
• SOLID
• OOP

How to use the Interface Segregation Principle in PHP. The fourth in a series on SOLID.

• Development
• PHP
• SOLID
• OOP

How to use Liskovs Substitution Principle in PHP. The third in a series on SOLID.

• Development
• PHP
• SOLID
• OOP

How to use Open Closed Principle in PHP. The second in a series on SOLID.

• OOP
• Development
• PHP
• SOLID
• OOP

How to use the Single Responsibility Principle in PHP. The first in a series on SOLID.