For Senior dev it is also good to think of the future and company environment. Business might know what feature they want to develop but they might not be aware of all the constraints and requirements. Security, scalability, modularity, testability and other properties.
Yes, always consider other devs, future problem solving and debugging. Don’t just implement the PDF mailer “directly” but first create separate route and view to see the blade template page for the invoice. Then implement PDF conversion, then the mailer part. All parts should work separately and be easily debugged, testable and documented. Document the functionality under docs/ folder as markdown pages so the next dev won’t hate you.
Senior devs often have a good overview of each part of a large project, placing them well for code reviews and knowledge of how one part of an app might affect others.
Great video! I'd be very interested in a video on how to orient yourself as a developer in face of ever more prevalent usage of AI in the development space
Next time I ask chat GPT that need a senior approach, I'll make sure to add this information from the video to the prompt and see the how the result can be different 😅😅 Just kidding.. So good to see many senior has also a different approach for the same cases sometimes.. They all good. We just need to starts somewhere.. Nice point of view ❤
It's hard to have ONE series or one example for senior, those would be VERY long videos or even courses. And actually I did make a few senior-level topics but unfortunately they were NOT popular. But I will think about finding another angle.
@@LaravelDaily may not be a complete series. Just point to subjects with fast examples. That collect ideas that can be followed by searching and developing.
@@LaravelDaily I'm sorry, there is a difference in expression across cultures. What I mean is that you can provide a general idea without needing to delve into details. For example, using cash in a simple video to illustrate its importance and impact on big data is sufficient. There is no need to create a detailed explanatory video. This would be enough to serve as a guide for every developer regarding the things they should focus on if they wish to develop themselves.
But this is what I've been doing over the years on this channel, I did have at least a few videos about caching. What you're suggesting is to combine 125 topics in one very long video. I've done similar things and I can assure that many people will NOT watch it.
One of my often types of tasks is to provide R&D about third-party integration in our existed infrastructure and services without any problems and downtimes, money costs, choose between a few of third-party software by props and cons, and after need to create PoC on second step.
Could you make a video about how to organize our time as developers? If we work 8 hours a day, how can we find time to learn something new or work on personal projects (for example, a JavaScript or C# course that requires 30 hours)? I often feel tired after work and struggle to dedicate even 1-2 hours to learning. Should I try to learn during working hours? Or, how can I better organize my work schedule to include time for things like unit testing?
first of all,dedicating 8 hours a day is for the company which helps company. But if you want to grow yourself you need to give time to your self growth which will help you in long run. if you grow your company will also grow. So it's important to make a time slot for your learning. You shouldn't feel tired because you are doing for your own growth.
@@Deadmanstrolln Laravel consumes a significant amount of resources for each request, and if the number of requests exceeds a certain limit, say 300 requests per second, we need to pay a lot for resources. However, plain PHP doesn't consume such resources, and even PHP itself is relatively weak compared to other technologies and languages. For example, Node.js consumes significantly fewer resources. Why should companies invest in Laravel when there are much better options available?
I don't think there are many companies that need to deal with 300 requests per second. And even then, there are solutions like Laravel Octane, scaling servers, etc. The usual performance bottleneck of Laravel projects is actually not Laravel itself, but poorly written DB logic/structure and Eloquent operations.
For Senior dev it is also good to think of the future and company environment. Business might know what feature they want to develop but they might not be aware of all the constraints and requirements. Security, scalability, modularity, testability and other properties.
Yes, always consider other devs, future problem solving and debugging. Don’t just implement the PDF mailer “directly” but first create separate route and view to see the blade template page for the invoice. Then implement PDF conversion, then the mailer part. All parts should work separately and be easily debugged, testable and documented. Document the functionality under docs/ folder as markdown pages so the next dev won’t hate you.
Senior devs often have a good overview of each part of a large project, placing them well for code reviews and knowledge of how one part of an app might affect others.
it’s also important to have both hard & soft skills on a high level for seniors imo
carlo ancelotti of programming
Looks like ancelotti but talks like pep
😂😂😂😂😂
Just wanted to mention it, saw your vomment😂
Lol
Great video! I'd be very interested in a video on how to orient yourself as a developer in face of ever more prevalent usage of AI in the development space
I did have a few videos on that topic recently, the most fresh one is here: ruclips.net/video/-vTK2EIWhNY/видео.html
Next time I ask chat GPT that need a senior approach, I'll make sure to add this information from the video to the prompt and see the how the result can be different 😅😅
Just kidding.. So good to see many senior has also a different approach for the same cases sometimes.. They all good. We just need to starts somewhere.. Nice point of view ❤
Thanks for this 👍
thank you
can make real scenario for Senior with practical examples , may be create series for that . thanks
It's hard to have ONE series or one example for senior, those would be VERY long videos or even courses.
And actually I did make a few senior-level topics but unfortunately they were NOT popular.
But I will think about finding another angle.
@@LaravelDaily may not be a complete series. Just point to subjects with fast examples. That collect ideas that can be followed by searching and developing.
Sorry I don't know how to "point to subjects with fast examples" :)
@@LaravelDaily I'm sorry, there is a difference in expression across cultures. What I mean is that you can provide a general idea without needing to delve into details. For example, using cash in a simple video to illustrate its importance and impact on big data is sufficient. There is no need to create a detailed explanatory video. This would be enough to serve as a guide for every developer regarding the things they should focus on if they wish to develop themselves.
But this is what I've been doing over the years on this channel, I did have at least a few videos about caching.
What you're suggesting is to combine 125 topics in one very long video. I've done similar things and I can assure that many people will NOT watch it.
One of my often types of tasks is to provide R&D about third-party integration in our existed infrastructure and services without any problems and downtimes, money costs, choose between a few of third-party software by props and cons, and after need to create PoC on second step.
I am working in a startup on a project and almost all the project features depends on me , do you think that pressure will make me senior fast?
Yeah, basically, I see two options: become senior or lose job :) #sorryNotSorry
@@LaravelDaily yeah I learned alot from that pressure and I don't want to waste the opportunity
Could you make a video about how to organize our time as developers?
If we work 8 hours a day, how can we find time to learn something new or work on personal projects (for example, a JavaScript or C# course that requires 30 hours)? I often feel tired after work and struggle to dedicate even 1-2 hours to learning.
Should I try to learn during working hours? Or, how can I better organize my work schedule to include time for things like unit testing?
I did have videos about time management, please search the channel.
If only we could prompt a youtube chat aí to find that video snd reference the link in-line as a comment
This is a nice idea@@elmalleable
first of all,dedicating 8 hours a day is for the company which helps company. But if you want to grow yourself you need to give time to your self growth which will help you in long run.
if you grow your company will also grow. So it's important to make a time slot for your learning. You shouldn't feel tired because you are doing for your own growth.
1º comment.😊
Sleeping at work
A senior engineer is someone who voluntarily takes on the miscellaneous tasks that lie outside of development, i guess.
just learn anything else like laravel . laravel is so bad . for performance
Why do you say that? In what applications is laravel noticably less performant than anything else?
@@Deadmanstrolln Laravel consumes a significant amount of resources for each request, and if the number of requests exceeds a certain limit, say 300 requests per second, we need to pay a lot for resources. However, plain PHP doesn't consume such resources, and even PHP itself is relatively weak compared to other technologies and languages. For example, Node.js consumes significantly fewer resources. Why should companies invest in Laravel when there are much better options available?
I don't think there are many companies that need to deal with 300 requests per second.
And even then, there are solutions like Laravel Octane, scaling servers, etc.
The usual performance bottleneck of Laravel projects is actually not Laravel itself, but poorly written DB logic/structure and Eloquent operations.
don't blame laravel, php, slow pc, or entire world if you write sh*tty code :)
Hello. The courses you have created are really great. I have some questions for you. Please send me a message.