It's really important When I was a student, I was choosing a programming language, reading a lot of books, and watching a LOT of RUclips videos, but it didn't work because I had no practice. My friend is making the same mistake - he just watches videos and doesn't build a project. When you create a project, you face errors, and that's a good thing! My advice for personal projects is to try to create something SMALL (you don't have to create anything big) and useful for someone (yourself, parents, friends, teachers, etc.).
I would tell him: yes, there may be some pkg for that. Read it, understand it, then evaluate whether it's actually needed and whether you need all it offers or if the subset of features you need are better off being written directly in the code. Remember, all code is a liability and subject to eventually breaking. Less packages usually yields easier upgrades.
I would tell myself, use laravel naming conventions to leverage laravel "magic". I learnt this the hard way, when I started didn't know how important it is. Also I would tell myself to split the code in smaller parts and moving them out of the controllers.
I suggest that Laravel, especially its documentation, should include more detailed information on each topic. Sometimes, I feel that the Laravel documentation addresses topics superficially, not comprehensively. It would be better to have more detailed explanations on the website to assist developers, especially beginners, during their learning process.
Advice to my fresher or younger self "Read code (think) again" before asking help on social network or forums. Because many times Solution is within error message This
Have you ever considered a lavalier mic for these types of videos Povilas? I know the format is relaxed / in your car so it might not be a priority. The audio is fine, but it definitely sounds like it's coming from your phone. Maybe the mic could add some finesse to it? Just a thought, appreciate your content nonetheless 👏
One more thing: It's fine to start learning Laravel without knowing PHP, and learning both at the same. Of course basics of programming are required, like: variables, loops, logic, etc. When you see working code - functions, classes, how it all interacts - you get the logic how it all works, and how you may use it for your project or task.
This can be a very slow way of learning since when the magic breaks and the new learner doesn't know what just happened or can't be able to know where to begin troubleshooting from, they get STUCK by the dead weight.
@@kennethkipchumba2532 When you go the academic-way - it totally can be slow. And going straight to the business - is one of the fastest ways to learn new things, and remember them well.
Speaking of "freedom" in Laravel. Eloquent or "pure SQL". Understandably, if there are simple links, one, two levels, and only one record or small record processing, eloquent is the best choice. But, reports, tables with many levels and links data. Things where there are many tables involved, growing links, at several levels. Eloquent or "pure SQL". By "pure SQL" I mean "DB::table()->leftJoin()". Not "DB::statement()". Like - eloquent. Dislike - "pure SQL". My vote.
One of my suggestions should be “Dont just read, but also try to build something.” Trial and error is always the best way to learn stuff.
It's really important
When I was a student, I was choosing a programming language, reading a lot of books, and watching a LOT of RUclips videos, but it didn't work because I had no practice. My friend is making the same mistake - he just watches videos and doesn't build a project. When you create a project, you face errors, and that's a good thing!
My advice for personal projects is to try to create something SMALL (you don't have to create anything big) and useful for someone (yourself, parents, friends, teachers, etc.).
I would tell him: yes, there may be some pkg for that.
Read it, understand it, then evaluate whether it's actually needed and whether you need all it offers or if the subset of features you need are better off being written directly in the code.
Remember, all code is a liability and subject to eventually breaking.
Less packages usually yields easier upgrades.
I would tell myself, use laravel naming conventions to leverage laravel "magic".
I learnt this the hard way, when I started didn't know how important it is.
Also I would tell myself to split the code in smaller parts and moving them out of the controllers.
Of course, naming convention is important!
love your insights. please share more of these kind of videos.
valuable. thank you
Thank you so much for your work
Thanks for these advises!
I suggest that Laravel, especially its documentation, should include more detailed information on each topic. Sometimes, I feel that the Laravel documentation addresses topics superficially, not comprehensively. It would be better to have more detailed explanations on the website to assist developers, especially beginners, during their learning process.
You are Awesome sir!
I would say "Don't over enginner your code unless it's necessary and makes sense to do so"
Advice to my fresher or younger self "Read code (think) again" before asking help on social network or forums.
Because many times Solution is within error message
This
Build a complete project and deploy.
13 years in development:
Absolutly consent
5th one is the goal of the match .
Have you ever considered a lavalier mic for these types of videos Povilas? I know the format is relaxed / in your car so it might not be a priority. The audio is fine, but it definitely sounds like it's coming from your phone. Maybe the mic could add some finesse to it? Just a thought, appreciate your content nonetheless 👏
One more thing: It's fine to start learning Laravel without knowing PHP, and learning both at the same.
Of course basics of programming are required, like: variables, loops, logic, etc.
When you see working code - functions, classes, how it all interacts - you get the logic how it all works, and how you may use it for your project or task.
This can be a very slow way of learning since when the magic breaks and the new learner doesn't know what just happened or can't be able to know where to begin troubleshooting from, they get STUCK by the dead weight.
@@kennethkipchumba2532 When you go the academic-way - it totally can be slow. And going straight to the business - is one of the fastest ways to learn new things, and remember them well.
Sir please create a free video on the starting journey of testing
I already have a series, look at playlists on the channel
❤
Speaking of "freedom" in Laravel. Eloquent or "pure SQL". Understandably, if there are simple links, one, two levels, and only one record or small record processing, eloquent is the best choice.
But, reports, tables with many levels and links data. Things where there are many tables involved, growing links, at several levels. Eloquent or "pure SQL". By "pure SQL" I mean "DB::table()->leftJoin()". Not "DB::statement()".
Like - eloquent.
Dislike - "pure SQL". My vote.
1 thing - never start with PHP 😂
Why are you watching this then?
❤