Unfortunately, I can't recommend any specific resources with the tips, as I’m not sure such a resource exists. It's important to realize that Laravel is built on several principles that are often considered anti-patterns, like Active Record, Service Locator (facades), and overuse of Traits. It even deviates from SOLID principles with its use of dynamic properties (magic methods/properties). Because of this, it's unlikely that someone of the caliber of Uncle Bob or the Gang of Four would write about these approaches. Personally, I’ve learned to work comfortably with these elements by analyzing my mistakes, reviewing existing solutions, and studying the source code of various packages. I also pulled together a wide variety of information from the internet, though I didn’t compile it into a single resource list. Sorry I couldn't help. And I will be grateful if you find something and share it. I would like to have some authority. So that my advice does not sound like "trust me, I know for sure"
And also, a great deal of advice and knowledge from my colleagues and friends. They taught me many things, and I am grateful to them. The first response may seem a bit self-centered...
what books or material do you recommend to know about all these standard ways of developing software?
Unfortunately, I can't recommend any specific resources with the tips, as I’m not sure such a resource exists. It's important to realize that Laravel is built on several principles that are often considered anti-patterns, like Active Record, Service Locator (facades), and overuse of Traits. It even deviates from SOLID principles with its use of dynamic properties (magic methods/properties). Because of this, it's unlikely that someone of the caliber of Uncle Bob or the Gang of Four would write about these approaches.
Personally, I’ve learned to work comfortably with these elements by analyzing my mistakes, reviewing existing solutions, and studying the source code of various packages. I also pulled together a wide variety of information from the internet, though I didn’t compile it into a single resource list.
Sorry I couldn't help. And I will be grateful if you find something and share it. I would like to have some authority. So that my advice does not sound like "trust me, I know for sure"
And also, a great deal of advice and knowledge from my colleagues and friends. They taught me many things, and I am grateful to them. The first response may seem a bit self-centered...