Events-Driven Architecture is awesome...until it isn't.

Embrace Modules, Engines, and other monolithic organization units

Interfaces are your friend. They provide clarity, extensibility, and make documentation easier.

Use the Service Container to your advantage. Think about how your classes, engines, and service classes will be used via the service container at the beginning.

Model Events are dangerous. I know it's controversial...but I've seen it fail too many times. If you do it, it should always be class based. It makes testing against it easier - architecture testing via Pest.

Utilize Model Permission Guards Extensively. Lock down database access based on roles and permissions.

TDD is King. I know it sucks, but you will be better off.

Be extremely wary of Livewire, it is tempting to transfer business logic to Livewire view classes.

Be extremely wary of Inertia.js. It makes life easy at the beginning. Some of its limitations cause problems later on.

Embrace the Manager Pattern, it's powerful...if you use it for good.