late mist
There's a ton of tutorials out there on how to make your first Laravel application, mostly "How to make a blog / api / todo list / twitter-clone" with CRUD. But what are the next steps when you've mastered basic MVC, routing, CRUD and deploying your first project? As a beginner, what are the next 2-3 concepts about Laravel that you should master?
naive quest
There's a section on the docs "digging deeper"
iron silo
Testing would definitely be good to learn, as you can add testing to even CRUD-only or CRUD-heavy apps.
late mist
There's a section on the docs "digging deeper"
Yes. It has 16 subheadings. Do you start at the top and aim to master them all? Do you prioritize 1 or 2 of the categories firsts?
naive quest
Yes. It has 16 subheadings. Do you start at the top and aim to master them all? ...
I prioritize by matter of what I need
iron silo
Yes. It has 16 subheadings. Do you start at the top and aim to master them all? ...
It’s not a step by step list. Pick a topic that interests you and drive into it.
naive quest
Best tip I can give to anyone: Stop overthinking, start coding
Or you're gonna be stuck in "tutorial hell" just reading about patterns, topics, concepts, guides for hours on end and with nothing to show
late mist
Of course, "it depends" applies, but what if I want to prove to an employer that I know more than just the bare-basics? What will an employer look for?
naive quest
Ask the employer.
Didn't you ask a similar question earlier today?
Or maybe it was someone else
late mist
I think that was someone else.
naive quest
Oh yeah it was someone else, but it was about basics. The same case still applies here: <#general message>
"Just learn everything" would be the answer, but it's impossible to learn and know everything. You're in a field that's ever evolving, the basics of Laravel are outlined, so is the "deeper" parts of it. Pick a topic of interest and move on from there, tinker, try and make stuff work.
If an employer needs something specific, you talk to them about it. Most good employers will also mostly not care what experience you have with it if they can tell that you have enough experience around other subjects to the point where they can invest time in you learning it while working
For example, my last employment they used Angular which makes heavy use of RxJS - Never used it before, but because I had experience with React/Vue they were like "ok you can pick it up" and it didn't matter in the end
late mist
My experience is that there's an abundance of "How to do the basics"-advice out there, but very few "These are the recommended next steps".
The Laravel documentation, Traversy Media, Laracasts, Laravel Daily, DevDojo, etc teach pretty much the same thing. It is a different kind of "tutorial hell" - every tutorial teaches you the exact same, very basic concepts.
Also, when applying for jobs, asking "an employer" doesn't necessarily apply, if you apply for 8 different jobs that all look for an experienced Laravel developer. Are there no general tips (except for maybe testing), except "It depends"?
naive quest
Because "experienced laravel developer" can mean different things per employer?
I've met employers who didn't even know what Laravel was, so to them knowing the basics would be experienced
iron silo
There’s no magic “advanced Laravel” checklist, no.
Anything past building a CRUD would be straying into “advanced”.
But there’s no threshold where you suddenly go, “Oh, that’s advanced now!”
If I were hiring, I’d say a knowledge of the service container and service providers would be a good one to have. I’d definitely be looking for tests being written, too.