Member Since 5 Years Ago

Experience Points

3,230 experience to go until the next level!

In case you were wondering, you earn Laracasts experience when you:

  • Complete a lesson — 100pts
  • Create a forum thread — 50pts
  • Reply to a thread — 10pts
  • Leave a reply that is liked — 50pts
  • Receive a "Best Reply" award — 500pts
Lessons Completed
Best Reply Awards
Best Reply
  • start your engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-in-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber Created with Sketch.


    Earned if you are a paying Laracasts subscriber.

  • lifer Created with Sketch.


    Earned if you have a lifetime subscription to Laracasts.

  • evangelist Created with Sketch.

    Laracasts Evangelist

    Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.

  • chatty-cathy Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

Level 2
6,770 XP
4 weeks ago
Activity icon

Started a new Conversation Storage Of Site Wide Configuration

Probably a simple and daft question, however ... When it comes to data that is used across the site and unlikely to change frequently (i.e. premise address, primary contact number and email), would this belong in a database 'settings' table or the .env file?

Activity icon

Replied to Data And Props Naming Conflicts

Thanks @piljac1 and @silencebringer for your input. I know this is one of those opinionated questions where asking 10 developers can result in 10 differing responses.

After considering the options and watching a few videos from some other developers in the Laravel/Vue community I opted for the scoped option.

data() {
  return {
    form {

A bit more verbose but it works for me.

1 month ago
Activity icon

Started a new Conversation Data And Props Naming Conflicts

When dealing with the naming of data and props in components, how do people deal with naming conflicts so that names still make sense but do not conflict?

For example, you might have a <user-information-form :user="{{ $user }}"></user-information-form> which displays information about a User and so pass the User through as a prop.

props: {
  user: Object

You want to enable two-way binding so create a data variable for this but can't name it user as that is already defined in props.

So what do people do in this situation, is there a convention? Do people prefix the variables (displayUser, localUser, mutableUser, etc.).

Or maybe scope the variable;

data() {
  return {
    local: {
      user: {}

Then use the scoped variable for binding this.local.user?

2 months ago
Activity icon

Started a new Conversation Multiple User Type Auth

I am creating a system where there will be different types of user. To keep things simple in this example lets say Staff and Users. What I am curious about is the 'best/better' method for storing the information about these types of user and handling their authentication. There seems to be split opinion as to whether to put these user types into separate tables and have separate auth management (login routes and workflow etc.), or keep it in a single table with a user_type which is used to reference a related table and reuse the routes, views and workflow.

I am curious to hear the opinions of people on Laracasts and their reasoning.