marketintelligence

Member Since 1 Year Ago

Experience Points
11,710
Total
Experience

3,290 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
103
Lessons
Completed
Best Reply Awards
1
Best Reply
Awards
  • 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.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer Created with Sketch.

    Lifer

    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.

  • Community Pillar

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

Level 3
11,710 XP
Feb
07
3 weeks ago
Activity icon

Replied to Architectural Advice On Re-usability

Sorry it wasn't clear what I meant. Hopefully I can explain it better below.

I now have a Laravel Application where everything is running. But we want to reuse the basis (such as a subscription management part, rights and permissions, user management, etc.) as well as certain functionalities such as managing events, inviting members to events, and the like.

I am mainly concerned with the strategy to make reusable parts from a Laravel application. I have read a bit about micro-services or is it more sensible to divide all functionality into Laravel packages, for example.

Does that clarify it with regard to the background of the question?

Feb
06
3 weeks ago
Activity icon

Started a new Conversation Architectural Advice On Re-usability

I have a platform that I would like to know your opinion about.

Suppose you have a current Laravel platform in which we use Laravel as API and the front works as a VueJs SPA, we use Laravel Sanctum for authentication.

The platform has a whole list of functionalities such as managing users and managing the members of organizations of users of the platform, the organization can also plan events in the platform and we have a payment street in which members of an organization have a wallet. available and can pay promotions from.

From the point of view that we have a solid foundation ( a sort like Laravel Spark is intended for), and we may also want to develop new SaaS applications. What is your advice in the strategy to be followed to make the current functionality reusable? What would you do?

Jan
21
1 month ago
Activity icon

Started a new Conversation Any Advice On Testing Traits

We have a challenge, we use a number of traits in our code that we use in several places.

We have created a generic livewire wizard component in which we use a HasSurveyQuestions trait, but that immediately presents the challenge, are you going to test the trait in every wizard you create? Or would you only test the trait because that trait is generic and it actually doesn't matter where you apply it.

What would you recommend?