So much this... I've been doing Software Dev for 26 years, PHP for 16 years, and Laravel for the last 2.5, and I learned something from this video. So I'd also add "Seniors, don't assume you know everything, and your way is the only way."
The delete action using "GET" instead of "DELETE" might expose the user to CSRF attacks. That one should be changed for security. (I hope this observation can be useful for someone).
@@digitalminister5687 Yes, I know, I just wanted to point out the potential security issue, that's all :) I also record videos and it's challenging if not impossible to cover everything in one video no matter the length.
Im experienced web developer, but a c# one. Have no idea why this video appears in my recommendation, but it's ASWESOME. For me It was a good overview of PHP/Laravel development). Without any experience I understood 100% of it! Thanks.
i agree with you on this statement "as junior dont be afraid to make mistake (but take responsibilty on that)" "as senior dont attack your junior (we have to start somewhere right)" huge respect to you!!
This means a lot of helpful to jr. developers to learn. I have seen many videos. many of video creators Assumes that you were aware about the mistakes that users do. but actually the fresher or junior developer wasn't aware of that. *And this is really fantastic video to identify mistakes and correct them*.
The command in PHPStorm to highlight the next occurrence of a word is Ctrl+G on Mac and Alt-J on windows. On vscode it’s ctrl+D. Rather than moving the mouse and highlighting line by line Great content!
Hello sir You are the most humble and kind person in the region. You always appreciate others for working hard instead of dominating them for mistakes, and helping them grow each time. I think your contribution to this growth of laravel is remarkable. Help is only help, whatever form it may be given, and I am grateful for your efforts and love.
I have completed my last project fully with query builder only. This video help me to under stand the standard of code. Thank you so much sir. You videos help me lot
@@mbparvezme Validation messages can be set in the Request Class created using " artisan make:request" command. Laravel will take care of the rest. And for the frontend you do everything same as before. Also check out the laravel documentation on "The Basic > Request" section it explains it beautifully. You can also use custom Rules inside the request class instead of if statements in the controller. 😉
@@0xshashwat Thank you for your reply. It was my fault. I just forgot to include the "Accept: application/json" header in the request. That is why it send me a response with a redirect (back). But with the appropriate header, I got the error message.
Very nice sir, most of the tutorials on net only deals with beginners things, ie how to start or more advance things, but you literally deal with minor problems which developers actually face, while developing something. I highly respect you for your efforts.
Well then.. This 'refactoring' went so fast, I felt bad I couldn't follow everything. Time to brush up on my Laravel skills again. Quality video by the way. THIS is how juniors improve and learn different code styles and refactoring.
Great video. As for multi-line edit. Just double tap ctrl, and use arrow down to select all lines. Hit "End" to get the cursor to the same location on each line. Now remove the middleware in one go.
Thanks for your videos Povilas, I am also beginner laravel Developer, i'm your fan, your videos are very helpful. When I start earning money i will obviously buy your " eloquent course"
Such a phenomenal idea for the video. This what I was looking for back when I started just a year ago. I always had a feeling that new/beginner developers want to see what a real application looks like, how every part of it looks like, not just some examples and basic principles. Or even see other beginners how they code and it all looks like. So interesting. I will admitted, I do have some mistakes in common with the "author" of the code you reviewed. You should keep doing videos like this, it's really useful in terms of improving and seeing that we all actually make common mistakes, I'm no different than many other guys who started. It's a normal learning process and we shouldn't be ashamed of our silly, but important mistakes. Really grate video sir. 🙂 Cheers
Awesome video, happy to see that I'm doing at least some of the things right, but even happier to see what is expected from me to write a better code in laravel.
Another note: if you're looking to refactor your routes, please take the time to make some quick feature tests that hit your routes so you can test when you change anything if something breaks and follow the errors to refactor it correctly.
Extremely helpful!! I started coding in Laravel a few months ago, and while I know how to get things done, this helped me learn how to do them the right way. Thank you!
If a resource route was used you might also run into the issue of not all the routes expected being present, which very well might be intentional as you might not need all of them. They are; index, create, store, show, edit, update and destroy. If any are not needed you can chain the "only" or "except" methods when defining the route: Route::resource('photos', PhotoController::class)->only([ 'index', 'show' ]); or Route::resource('photos', PhotoController::class)->except([ 'create', 'store', 'update', 'destroy' ]); respectively. If a resource route is defined and all expected methods are not accounted for then artisan will throw an error. This is a great vid, just hoping to help out too if i can.
Povilas, another great video. I can't get enough of praising and thanking him for his work. And I think your guidelines are not just for juniors! Congratulations!
Great video, love the format. Never knew about the eloquent "when" method. Good way to plug gaps in your knowledge
4 года назад+1
This video format is great for the channel as the comment/view ratio it gets. Some stuff is obvious but other is just awesome. Keep this series coming along.
really incredible video quality, learning from your lessons constantly. At work, I recommend your videos to colleagues. Thank you for such quality content! hello from Russia, city of Stavropol: 3
Pretty good review. Only thing I would have said more explicitly is that Material:all() returns a collection, so the where is using PHP code to do its job. It may not be as obvious to the junior that the all() sets up the query AND fetches, where as the where function of the Eloquent model is simply utilizing a query builder and get does the fetch. The confusion mostly stemming from the collision of some function names in collections vs query builder for eloquent.
very very helpful sir you help me very much in laravel as i am also a laravel developer . Really thanks for your knowledgeful videos and keep ahead sir one more time thank you very much
This chanel is gold... Great video, as always 🔥 For this code review, I would also go for constants, instead of hardcoding Roles ID everywhere. Like ROLE_MEISTER = 0, and so on. Should make the code way more readable.
In PHP Storm you can use "Alt+J" to select next occurrences of the selected code or use "CTRL+Shift+Alt+J" to select ALL occurrences of the selected code.
Yeah, this one took longer time to produce than I expected. Started with idea that "I'll just give a few tips in 5 minutes", and published this video 4 hours later :)
You helped me alot with the $requests... I did it the same way as you mentioned but i left it inside the function what felt tottaly wrong and now i know why i had this feeling all the time
Thanks. It was very helpful. A lot of tips that I think about every time when write code like "How to do in this situation" or "How it should be in correct way"?
Great video, need more of this unique learning, particularly useful for any dev level. Amazing advice to junior and senior at the video introduction. 👏
@@PovilasKorop I didn't say it is bad 😄 Since it is one of the ways to pass data to view, it is valid. But at my job we don't use it, how people say "Compact is hard to maintain and is unnecessary" What I think is "hard to maintain" is that it will not tell you if given string refers to unset variable. And "unnecessary" is that compact looks like "beatiful way" to simply pass data, but you could do the same think with just passing array
"Juniors don't be afraid to show your code. Seniors don't attack the juniors that the code is bad. We all start somewhere."
So much this... I've been doing Software Dev for 26 years, PHP for 16 years, and Laravel for the last 2.5, and I learned something from this video. So I'd also add "Seniors, don't assume you know everything, and your way is the only way."
@@JimOHalloran Every day there is new oppurtunities to learn things, we shoudn't feel ashamed to do so !
Absolutely, thankfully my team lead adopts this mentality as well. Such a good quality to have in leadership and development in general.
The delete action using "GET" instead of "DELETE" might expose the user to CSRF attacks. That one should be changed for security. (I hope this observation can be useful for someone).
buen dato , maestro.
3:54 he mentioned it
@@digitalminister5687 Yes, I know, I just wanted to point out the potential security issue, that's all :) I also record videos and it's challenging if not impossible to cover everything in one video no matter the length.
styde needs updated videos on laravel 8 ;)
John Smith what does that have to do with this video? And FYI I do have tons of videos in L8, just not in my RUclips channel.
Yes ! Please ! More code reviews videos ! As a junior I can't state how valuable this is. Thanks for everything !
I liked the video format. And today I noticed that I'm not a junior anymore.
Lmao
Omfg. This is like those "very satisfactory" videos with people slicing colored clay, but with coding.
Such a rewarding feeling to watch.
Im experienced web developer, but a c# one. Have no idea why this video appears in my recommendation, but it's ASWESOME.
For me It was a good overview of PHP/Laravel development). Without any experience I understood 100% of it! Thanks.
Your one video > Tones of Learn laravel from strach for Inermediates.Thank you Sir, have a better life everyday.
i agree with you on this statement
"as junior dont be afraid to make mistake (but take responsibilty on that)"
"as senior dont attack your junior (we have to start somewhere right)"
huge respect to you!!
i just watched till 1:13 and i start loving you.... This is how juniors shud be treated... Love You Sir.
This means a lot of helpful to jr. developers to learn.
I have seen many videos. many of video creators Assumes that you were aware about the mistakes that users do. but actually the fresher or junior developer wasn't aware of that. *And this is really fantastic video to identify mistakes and correct them*.
The command in PHPStorm to highlight the next occurrence of a word is Ctrl+G on Mac and Alt-J on windows. On vscode it’s ctrl+D. Rather than moving the mouse and highlighting line by line
Great content!
Hello sir
You are the most humble and kind person in the region. You always appreciate others for working hard instead of dominating them for mistakes, and helping them grow each time. I think your contribution to this growth of laravel is remarkable.
Help is only help, whatever form it may be given, and I am grateful for your efforts and love.
I have completed my last project fully with query builder only. This video help me to under stand the standard of code. Thank you so much sir. You videos help me lot
I've never written a line in PHP but still watched till the end, you never know when you gonna need this.
Great review, very satisfactory.
That $request->validated() and $fillable combination was on another level. Got to learn something new 😄
@@mbparvezme Validation messages can be set in the Request Class created using " artisan make:request" command. Laravel will take care of the rest. And for the frontend you do everything same as before.
Also check out the laravel documentation on "The Basic > Request" section it explains it beautifully. You can also use custom Rules inside the request class instead of if statements in the controller. 😉
@@0xshashwat Thank you for your reply. It was my fault. I just forgot to include the "Accept: application/json" header in the request. That is why it send me a response with a redirect (back). But with the appropriate header, I got the error message.
Very nice sir, most of the tutorials on net only deals with beginners things, ie how to start or more advance things, but you literally deal with minor problems which developers actually face, while developing something. I highly respect you for your efforts.
after 7 months of coding in laravel I finally got a hang of its basics... but this video shows me I just scraped the tip of the iceberg...
I am new to Laravel and some of these things are how I coding with Laravel, some are new and I'm excited to get more.
Well then.. This 'refactoring' went so fast, I felt bad I couldn't follow everything. Time to brush up on my Laravel skills again.
Quality video by the way. THIS is how juniors improve and learn different code styles and refactoring.
Eres grande amigo. No porque sepas mucho, sino por darte el tiempo de ayudar a los que saben menos. Saludos desde Chile.
Liked this video? I have many more: subscribe to my 30+ Laravel courses laraveldaily.com/courses
Amazing concept! Please do as many videos as you can easily. This is great content. Keep up the awesome work. 👍👍👍
I really enjoyed and learned watching this one as a junior programmer!
after watching this video i’am not a junior developer anymore 😁 , more videos like this sir. this is awesome, thank you povilas ❤️
Great video. As for multi-line edit. Just double tap ctrl, and use arrow down to select all lines. Hit "End" to get the cursor to the same location on each line. Now remove the middleware in one go.
or just hold alt as your move the cursor
Thanks for your videos Povilas, I am also beginner laravel Developer, i'm your fan, your videos are very helpful. When I start earning money i will obviously buy your " eloquent course"
Love code reviews like this! Please do more. It's a great way to learn. Thanks!
Please make this into a more regular series, very helpful! Thank you.
Such a phenomenal idea for the video. This what I was looking for back when I started just a year ago. I always had a feeling that new/beginner developers want to see what a real application looks like, how every part of it looks like, not just some examples and basic principles. Or even see other beginners how they code and it all looks like. So interesting. I will admitted, I do have some mistakes in common with the "author" of the code you reviewed. You should keep doing videos like this, it's really useful in terms of improving and seeing that we all actually make common mistakes, I'm no different than many other guys who started. It's a normal learning process and we shouldn't be ashamed of our silly, but important mistakes.
Really grate video sir. 🙂
Cheers
yes please do more refactoring session. Thank you!
Thanks , boss these kind of videos have great tricks... we need more and more
It helps us a lot as a junior Dev. please keep Reviewing .
Awesome video, happy to see that I'm doing at least some of the things right, but even happier to see what is expected from me to write a better code in laravel.
Another note: if you're looking to refactor your routes, please take the time to make some quick feature tests that hit your routes so you can test when you change anything if something breaks and follow the errors to refactor it correctly.
Extremely helpful!! I started coding in Laravel a few months ago, and while I know how to get things done, this helped me learn how to do them the right way.
Thank you!
If a resource route was used you might also run into the issue of not all the routes expected being present, which very well might be intentional as you might not need all of them.
They are; index, create, store, show, edit, update and destroy. If any are not needed you can chain the "only" or "except" methods when defining the route:
Route::resource('photos', PhotoController::class)->only([
'index', 'show'
]);
or
Route::resource('photos', PhotoController::class)->except([
'create', 'store', 'update', 'destroy'
]);
respectively.
If a resource route is defined and all expected methods are not accounted for then artisan will throw an error.
This is a great vid, just hoping to help out too if i can.
Loved your disclaimers!! Great video! Thanks for sharing. I'm also a junior developer and learning a lot from your videos.
Povilas, another great video. I can't get enough of praising and thanking him for his work. And I think your guidelines are not just for juniors! Congratulations!
Great video, love the format. Never knew about the eloquent "when" method. Good way to plug gaps in your knowledge
This video format is great for the channel as the comment/view ratio it gets. Some stuff is obvious but other is just awesome. Keep this series coming along.
I haven't done Laravel in years, but it was still interesting to watch :-)
really incredible video quality, learning from your lessons constantly. At work, I recommend your videos to colleagues. Thank you for such quality content!
hello from Russia, city of Stavropol: 3
Thanks alot Sir
This video is just so golden for me
Will sure watch more of this kind of your videos 🔥🔥🔥
I don't even know what the heck Laravel is, but that is a neat video format.
🥺
As a web developer in 2021, If you really don't know what Laravel is, you have a problem buddy!
Can you please make more refactoring videos like this? please!! It was soo good!
Please make more videos like this!
I loved to check what I am doing wrong and how to fix it and make it a better code !
Pretty good review. Only thing I would have said more explicitly is that Material:all() returns a collection, so the where is using PHP code to do its job. It may not be as obvious to the junior that the all() sets up the query AND fetches, where as the where function of the Eloquent model is simply utilizing a query builder and get does the fetch.
The confusion mostly stemming from the collision of some function names in collections vs query builder for eloquent.
Nice video and so many tricks and advises in just 20 minutes. Thanks
Wish I could like this video 10x. What a great tutorial
Thank you this was awesome! As someone just refreshing their Laravel knowledge I learned so much
Cool video concept. Definitely do more of these as they’re interesting. I learnt a few things too 🥳
This is really great, thank you. It's embarrassing to me that you probably just wrote more code in 20mins than I wrote all day today.
very very helpful sir you help me very much in laravel as i am also a laravel developer . Really thanks for your knowledgeful videos and keep ahead sir
one more time thank you very much
Refactoring is like ointment for my soul. I don't even use php but this is such a great idea for youtube content.
You really boost the morale for LARAVEL for all junior devs.
Keep it up sir. I always wait for your videos. I learnt more things in laravel.
This chanel is gold... Great video, as always 🔥
For this code review, I would also go for constants, instead of hardcoding Roles ID everywhere. Like ROLE_MEISTER = 0, and so on. Should make the code way more readable.
Wow, I don't even code in Laravel but I couldn't stop watching. I wish there was something like this for code in Ionic, Angular, Vue or Firebase.
Hope this series got more video. very helpful for all. thanks a lot.
Thank you so much.. You are doing great things for beginners... Keep it up
Nice video, very helpful for junior laravel devs
Details that can simplify your life a lot!
Very cool how you give tutorial, thanks for the video man!
Thank you for the video. We need more like this. Keep it up!
In PHP Storm you can use "Alt+J" to select next occurrences of the selected code or use "CTRL+Shift+Alt+J" to select ALL occurrences of the selected code.
Thanks a lot . Please , make more video like this. It's very educative.
I was just checking about Today's video 5 minutes ago 😁. Now here it is. Thank you Povilas.
Yeah, this one took longer time to produce than I expected. Started with idea that "I'll just give a few tips in 5 minutes", and published this video 4 hours later :)
Laravel daily sir, it help us alot because we are junior
We need more this type of videos. Thank you.
Best and crystal clear tutorial, thanks a lot 🙏
You helped me alot with the $requests... I did it the same way as you mentioned but i left it inside the function what felt tottaly wrong and now i know why i had this feeling all the time
Awesome video, perfectly explained, easy to understand, high value tips
I don't even code on PHP but I enjoyed the video, mostly for the lessons on organization and cleaner code.
I love these , I hope you still make them
I've made a lot of them, until I started repeating myself. See the Playlists of the channel, there should be one with reviews
the "store" method review i like the most
big thanks for you , you are the best in youtube truly
we need more videos like this .thank you for this video
More of this, please! I am just starting in the laravel world :D
simply, LEGEND !
Thanks, I learned a lot ...
This tutorial is very helpful!
Thank you so much!
Great Video. I would love to watch more videos like this.
This was really great, had to pause a lot to think... :). Really useful to see.
Please create more videos like this. This is so helpful.
wow , it's amazing , thank you very much , I got a lot of information in this video
Awesome! Really really great idea for video. Practical examples...
Thank you teacher .. please do this more
Great video,we need more videos like this
Thanks. It was very helpful. A lot of tips that I think about every time when write code like "How to do in this situation" or "How it should be in correct way"?
useful, its always nice to watch videos like that one
It very help me as baginner aravel code. Thank you sir
I just learned how to use in_array, thank you very much :)
Me too
What a video! Thanks! It 'was so useful!
your youtube channel is very informative
Great video, need more of this unique learning, particularly useful for any dev level. Amazing advice to junior and senior at the video introduction. 👏
need more like this. Code Review. Thanks for this share
Thank you so much ! so interesting to see ! :D
thx povilas, really awesome, we want more and more videos like this videoo
Thanks for the wonderful video.what I have been looking for.
This video inspired me to learn more
Just one small tip for passing data to view, instead of with() I would use compact().
Yes, great tip.
@@LaravelDaily As I know compact() is not good too, better is to just pass variables with view
'return view(view', [ 'variable1' => $something ])`
@@Minepuffik why compact is bad?
@@PovilasKorop I didn't say it is bad 😄
Since it is one of the ways to pass data to view, it is valid.
But at my job we don't use it, how people say "Compact is hard to maintain and is unnecessary"
What I think is "hard to maintain" is that it will not tell you if given string refers to unset variable. And "unnecessary" is that compact looks like "beatiful way" to simply pass data, but you could do the same think with just passing array
@@Minepuffik But that's exactly the purpose of compact function, to save your time and make your code cleaner.
What precise and well explained piece of art coding ! Many thanks, please do more, bad habits need to be corrected, even on seniors devs !
You are doing nice work in this video. I like it