Always good to provide real world examples from open source projects. Gives us context on how it's used in the real world. Too often tutorials only show concepts in the abstract.
Thanks for revisiting and really appreciated your time and loving laravel, and PHP 😍 I have been following you and you always updating things when its upgraded...
Respect from Pakistan. I have sensed you are way smarter than usual course creator, you knoe how to market by solving pain points of customers. In this example, you will wi hearts by "just" renaming course titles along with course cointent itself. Povilas = Hard work and smart work.
I will still continue videos here on RU-vid. With courses, there's a tradeoff: if I continue with video courses, then I will release 2x fewer courses and most of them would be not updated from Laravel 8/9.
@LaravelDaily I completely agree with the rational, it makes perfect sense. If I'm being honest I think I learn more from the written courses as they seem to be more information dense
Text courses are definitely the way to go. I like the fact that when I run into an issue or am confused about something, I'll remember it was talked about in the course and with it being text, I can easily go back and find it. With videos, not so much. On the same topic, maybe it'd be possible to add a "Search within Course" feature to LD? Great work as always, Povilas and team!
Hm, interesting proposal. We have a general global search but it works pretty poorly for such cases. Could you give an example of a query string for this case, and for which specific course? We would brainstorm from there.
@@LaravelDaily By "query string" I assume you mean a keyword that you can search for within an existing course for testing purposes? 🙂If so, "artisan" within "[NEW] How to Structure Laravel 10 Projects" should be good as it's mentioned quite a few times (both in text and code blocks).
Povilas, in a situation where you'd have methods that differ from laravels controller conventional methods, for example, an export or even a multi-delete method, where would you suggest putting those in the project? I'm having trouble figuring out how to organize my project in a situation like this.
@@LaravelDaily but placing every method in the same controller like this wouldn't make it scale badly? Wouldn't be better to, for example, make an invokable controller for each of those out of convention methods?
This is the way I structure: from routes, going to controllers. Controller have to do something then I call action class always with DTO as parameters (UserDtoFactory::from_request()) Action class is the main executor, it can call other actions, but call also service class which is responsible for some computations. Action always have try catch block which throws custom ActionnameException (there’s an error executing user creation) To handle db, I use a class called Repository which has two methods. command() which returns an instance of Command, queries() which return instance of Queries Both class have methods to deals with Eloquent commands and queries. If tomorrow I want to use another db, I just create two other classes Command and Query with same methods like other (helped by interface)
To me, personally, it sounds way overcomplicated for typical projects I work with. So I wouldn't want to show it on this channel, and it wouldn't even be possible to have a QUICK review without explaining all the pieces and WHY they exist. But if it works for you, then great!
Hello Mr. Povilas, this course must be great, but I learn better from a video course, have you thought about making it a video course, or making other courses in video format?
I did shoot courses in video format, at first, for many years, but in 2023 I switched to text because that way the courses can be always updated quickly, also I can release more courses. And, honestly, most students say these are easier to read because you can skim quickly and find only relevant information, and you can't do that with video. But I will keep shooting RU-vid videos on this channel, just not in the form of courses.
@@LaravelDaily Ok i understand, you are right, you do a really great job, your videos have taught me a lot and will definitely teach a lot more, thank you!🙏
@@akhelijmohamed1063 Respectfully, I disagree. More often than not, polished thumbnails lead to lackluster content. (Laracast would be an exception, of course.) I like that this channel focuses all of its attention on developing great content. No time is wasted polishing the things that don't really matter. I find that refreshing.
@@nilpo you are right, thats why they just have to not fall into the same trap. In Morocco we say "زين تبيع" which mean "Beautify to sell". What I am saying is that for them to allow more people to enjoy this kind of high quality courses, they need attractive thumbs. The clarity of the content should be also taken care of like they always do.
I think you complicating the codebase by creating many files unnecessarily. This way no suitable for all kind of project, the seperation of concern is wasting time by wasting time to seperate and jumping many files on vscode to do a task its time to think out of the box for old php developers. Just try nodejs express and change the way of thinking. Many old php developers are blindly following some rules or principles (like solid..) without any benefit and make it more complicating thins. Same state in laravel, making a problem (many bloatware file like config files seperated by seperation of concern principle) and introduced a new version (11) as the solution 😂
