@@JustSteveKing Thank you so much ! Because i've learned things on my own and when i need it, that's not the right way. So code architecturing is really useful for me
@@JustSteveKing Also i was wondering, sometimes in your CRM you wanna track user activity, and keep some history of changes. How would you implement that ?
I never understood why people keep calling on the repository pattern, in most cases it adds or simplifies nothing, just adds another layer. Unless im missing something. The only argument ive heard is in case you want to migrate away from eloquent, but realistically, that never happens.
Those sessions are amazing 🤩
I'm glad you're enjoying them! Always open for requests too if there's something I can help you eith
@@JustSteveKing Thank you so much ! Because i've learned things on my own and when i need it, that's not the right way. So code architecturing is really useful for me
@@JustSteveKing Also i was wondering, sometimes in your CRM you wanna track user activity, and keep some history of changes. How would you implement that ?
@@julienSibille that mostly depends on what sort of thing you want to track! If it's basic auditing, then I'd use the Laravel audit package
@@JustSteveKing Ok thanks, i'll take a look to the package !
I hope you upload at git 😬
I never understood why people keep calling on the repository pattern, in most cases it adds or simplifies nothing, just adds another layer. Unless im missing something. The only argument ive heard is in case you want to migrate away from eloquent, but realistically, that never happens.
in addition, this is also about Concept Separating and also adherence to the rules of the SRP (Single Responsibility Principle)