/explore
|
You are here 
|
nodogmablog.bryanhogan.net | ||
| | | | |
tomasvotruba.com
Regarding Laravel, one of the biggest "no"s in 2022 was how it handles passing services around the project. I'm not talking about the facades or active records but **the static reflection container**. At first, it raised my blood pressure - we have a dependency injection, and everything must be passed via the constructor, right? Then I remembered a wise saying: "There are no best solutions, only trade-offs." |
|
| | | | | ||
| | | | |
www.thepollyproject.org
|
|
| | | | | ||
| | | | |
lenholgate.com
[AI summary] The post explains the concept of Dependency Injection as a software design pattern to reduce coupling and improve flexibility through various injection methods like constructor injection. |
|
| | | | | ||
| | | | |
tomasvotruba.com
Another anti-pattern that deserves more attention than it has. I often see this in Symfony projects I consult and when I ask the dev *why* did he or she choose listener over subscriber, they don't really know - "it was in the Symfony documentation, you can read it there". Not good enough. **So why you should never use a listener?** |
|
| | | |||
