Intéressant comme pattern, je tente un implémentation simple avec les events doctrine
CRAP (Change Risk Anti-Patterns) métrique, à creuser
Pourquoi l'héritage peut-être mauvais ?
Collection d'anti pattern en POO.
Poisson distribution
Principe du moindre étonnement en P.O.O.
How did we get from 'Program to an interface, not to an implementation' to 'Just slap an interface on there, it's the fashionable thing to do'?
DORA is the largest and longest running research program of its kind, that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better organizational performance. Important à lire.
Diátaxis is a way of thinking about and doing documentation. À lire
In his book, Domain-Driven Design: Tackling Complexity in the Heart of Software, Eric Evans proposes a 4-tier architecture to allow isolation between the Domain Layer which holds the business logic, and the other 3 supporting layers: User Interface, Application, and Infrastructure.
This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned about Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series.
Bonne base de connaissance, à lire
Using the I prefix or Interface suffix for interfaces, as well as Abstract for abstract classes, is an anti-pattern. It has no place in clean code. Differentiating interface names, in fact, obscures OOP principles, introduces noise into the code, and complicates development. Here are the reasons. Je n'ai toujours pas tranché