How to be an Intermediate Laravel Developer

Actually I was going through the twitter one day. Then I saw a tweet by Shruti Balasa and in that tweet I found something very amazing. That was what is the important things that a mid-level laravel developer should learn or should not miss basically.

So, Then I thought that why not to write an article on this. So, here's a list that I have created from that article. If you do want to visit the tweet I'll embed that below.

https://twitter.com/shrutibalasa/status/1585221677117739008

What with this tweet I found a content Idea that let's write about the mid-level concepts of laravel.

Well, Let's come on the points

Testing

Testing I have heard a lot. I usually watch Laravel Daily So hearing about testing normal. And obviously If you are thinking about to boost your career then you should have testing skill in your resume as well. Because I personally experienced that having a skill of testing and speaking english company think twice to leave the developer Rather than you also good at building logic. Only testing will not make a good or mid-level developer and in sense this concept of testing in Laravel is very popular because testing saves a lot of time.

Learning to Write Advance Queries

Well, This is the question from Povilas Korop. And I also do consider him a good teacher as well. If you do want to watch his videos can go to youtube and type Laravel daily. In there he teach about advance things about Laravel. By following his videos you can really improve yourself this what I think. But let's come back to the point.

Writing advance queries means creating big relations and managing them. You could take an example from any ecommerce website where we used manage big relations between models. And I think this is where our learnings can increase. So, Learn to write advance Eloquent queries in order to be a mid-level good laravel developer.

Events & Listeners and Observer

So, Basically in third we will know about the Events and Listeners after that we will come to Observer.

Events and Listeners are a magic kind of functionalities that works in very smart way. Let me explain for example, you are registering the User and want to send him a welcome notification you can do it through Events and Listeners very smartly. If you are not familiar with events and listeners concept yet then you can go to official docs - Events in Laravel

Observers are also pretty same thing to Events but there's a difference that comes in the both of the ways that Observer is only related to a particular model. If you are performing any crud operation with a model and want to fire some logic without putting into the controller then observers are good way.

Example: You are registering a user and want to send a welcome notification you can do it with Observer easily.

Now, you will think that same example I gave in event so thing is that Events and Observers are more likely same but In events we manage broader things. Like sending notification to different roles putting some extra logic. But Observer is mostly a under the hood magic for particular model.

Moving logic to Services/Actions

Basically, I am not completely in the favor of doing this. Because if you have something really big to implement and to use widely. So that kind of logics you can keep into your services directory. Otherwise it doesn't matter that much if you are just building a crud or something like crud. So, do follow these things also after reading this and In order to become intermediate don't put your two lines in Service 😂. I mean don't try to be over smart.

You can visit this repositery on Github if you want to know more about how to keep your controller code clean if you are using something widely.

Github Open Source Project: Skuul

Queues in Laravel

Queues are time saver. I have personally used queues in my freelance projects. well, I was working on an application in which I used to send notification that was taking so much of time in loading. For example I want to send mail then if you will send then that will take a lot of time and if you can't wait 5-6 seconds then this is where queue that means jobs comes in.

You can create Job and Queue them in database or some other connections provided there. And it will be running automatically in the background. This is actually a time saver.

You can read more about queues on Laravel official documentation.

Read some more Laravel Tips

Conclusion

I might have missed a lot of things but in that case you can go this tweet that I have mentioned above otherwise you can read this notion page I have made a list there also

After putting some more point here in front of you. I came to the point that If you want to grow your knowledge more and more there plenty of things in Laravel that support your dream to expert at it. But it requires curiousness to discover new things daily with your work.

For single logic implementation there so many ways to do the same thing. So, You can be a smart programmer as well. Thanks.