Anonymously
What’s do you look for in a developer when hiring?
I wrote a small blogpost on that, which you can read here: freek.dev/2634-my-interview-questions-when-hiring-a-front-end-back-end-whatever-developer-at-spatie
Anonymously
What’s do you look for in a developer when hiring?
I wrote a small blogpost on that, which you can read here: freek.dev/2634-my-interview-questions-when-hiring-a-front-end-back-end-whatever-developer-at-spatie
Anonymously
Hi, Freek, is freek your real name or you call your self because you are a tech freak
Hahaha, excellent question.
My legal name is Frederik. My nickname is Freek, which is a common name in Belgium and The Netherlands.
I do consider myself a tech freak as well 😄
Anonymously
I see that in most of your projects, you are using React JS, is there anything that makes React favorable for you compared to Vue JS?
My colleague Seb wrote some good thought on this subject: sebastiandedeyne.com/why-i-prefer-react-over-vue
How much time are you planning to stay in Dallas buddy?
Before Laracon US, I'll be already at Laravel Live Denark, and I don't want to stay away tooo long. So in Dallas, I'll probably only stay one extra day after the conference.
Anonymously
You mentioned on 1billion.spatie.be
that "Laravel-permissions is our most popular package, yet we never use it ourselves." This raises curiosity: How do you manage permissions in the large projects you develop?
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.