Freek Van der Herten

@freek

Laravel permission is an excellent choice if you need dynamic permissions. As in: an admin should be able to create a type of permission.

For our projects, we don't need that. We know ahead of time which permissions are needed. In that case, using Laravel's standard authorization features is good enough, We mainly do checks using policies.

Freek Van der Herten

@freek

There's something to be said for both cases.

Validation in form requests is to make sure that user input has a valid structure (for example: an email has the right format). Validation in actions is mostly to check business rules (is this specific email adres valid for this specific actions).

There's indeed a big grey area here.

Freek Van der Herten

@freek

The only hard requirements are knowledge of Dutch and that you are able to be present in our office 2 or 3 times a week. We believe these two points are important for our company culture.

When hiring somebody, I usually not focus on hard skills, but more on soft skills and passion. If you have those, there's a high chance that there is potential to fit in our team.

I also wrote a bit on this topic on my blog: freek.dev/2634-my-interview-questions-when-hiring-a-front-end-back-end-whatever-developer-at-spatie

Freek Van der Herten

@freek

I’m probably a bit biased but Laravel Beyond CRUD is pretty good 😄
laravel-beyond-crud.com

Freek Van der Herten

@freek

Great question! Create a package that you are going to use yourself. This way your motivated to make something that works well, and maintain it in the long run 👍