laravel-best-practices

Eager load relationships with `with()` before iterating, and constrain the eager load to only needed columns while keeping the keys Eloquent uses for matching. Enable `Model::preventLazyLoading()` in non-production environments to surface violations during development.

Organize controllers around one resource using standard actions like index, show, store, update, and destroy, and use implicit route model binding. Extract substantial business logic into action or service classes, and consider modeling custom verbs as separate resource controllers.

Use a form request when validation or authorization is substantial, reused, or clearer outside the controller; its `authorize()` method can also enforce access. Inline `$request->validate()` remains appropriate for small, endpoint-specific rule sets.

No. `$fillable` controls which attributes `create()` and `update()` may set, but it does not validate values or authorize the operation. Combine it with validated input via `validated()` or `safe()` and explicit authorization through policies or gates.

Set `retry_after` longer than the worker's `--timeout` so jobs are not reserved twice, and use `$backoff` arrays for progressively longer delays on transient failures. Make important jobs idempotent, since workers can stop after side effects but before acknowledging a job.

Global scopes silently modify every query on a model, which complicates debugging and hides rows from admin panels, reports, and jobs. Prefer explicit local scopes and reserve global scopes for universal constraints like soft deletes or multi-tenancy.