I appreciate your pragmatic approach to web development, embracing it as a typical developer. In our industry, there's a common tendency for everyone to claim expertise, and there's a misconception that complexity equates to superiority. I've personally experienced judgment from 'senior' developers for using a Git GUI client instead of the command line, so I can relate to this challenge. Ultimately, prioritizing tools that enhance coding efficiency and faster delivery is far more valuable than adhering to norms that might create unnecessary friction based on outdated perceptions of how 'real developers' operate.
Glad to hear you relate to me! I would say I’m a decent enough developer, but I still prefer when things are magical and easy instead of having to configure Docker or mess with a bunch of server settings. Use the tools that help you become faster at building things. ☺️
I really love your channel, also js developer swicthed to Laravel. I'd appreciate if you'd put more content around these js developer transitioning like us, topics like PHP Crash course, Laravel Livewire serious, Creating Composer CLIs, Laravel project folder strucure and OOP, and more. Thanks bro.
I really appreciate your content, but as a devops and ex php developer, I would say learning Docker and taking the time to understand where and HOW your app runs, is as important as knowing how to write it. All those SaaS hide complexity away from you and on scale debugging becomes a nightmare. Not to mention vendor-lockin. A docker image is vendor agnostic, can be deployed everywhere and you got to tune it as a developer. Cheers.
Thank you for the support! ☺️ I definitely agree with you there. Even using Laravel Vapor, I still have a lot of flexibility using Docker to install extensions. I do think there’s benefit in finding solutions that allow you to get up and running with and without docker. But I still have a lot to learn with Docker. ☺️
Fascinating insight into options out there for low friction deployment. I am intrigued by Bref and will subsequently look more into this - the idea of a Laravel app hosted as if twere a function and charged for when it is used and not for when it is not. Seems too good to be true but certainly worth the time to try it out. Thanks for all the tips, this is great. I would recommend to anyone learning Docker at least if not containers in general and how to use these in a development life cycle. This leads into production delivery and as such is a good introduction to production concerns. It is like an 'interface' if you would to making your apps service ready and having consistent, repeatable and reliable environments from dev => prod. I suppose I would say that, having learnt and used Linux since before y2k when it was slackware and on 20+ floppies but I'm on old curmudgeon i suppose. Ha ha !
Thanks for the insights and comments Jon! I’ll admit that I wish I learned how to better use Docker earlier, and even with Laravel Vapor I still deploy using Docker to make use of a few extensions that aren’t available out of the box. As someone who is still learning and only has experience pointing servers to a Git repo, your kind knowledge is exactly what more new developers need! Have to learn how easy we have it before we learn how to make it easy.
@@joshcirre absolutely, thank you for your kind words we are all still learning I think and if we are not we should be. I like you spent a lot of time in the Javascript SPA ecosystem and still do, thinking the old ways routed in Wordrpress and traditional CGI server based was no longer of relevance however PHP and Laravel have fresh approaches like livewire that challenge this thinking. It is thanks to your comments and your channel I am now reviewing this and am looking to use Laravel for a use case we have right now, so thanks for your content and hard work and please do keep up doing what your doing. I've learnt a lot and certainly many others will too.
What are your thoughts on the objection to Laravel which I've stumbled across that its release cycle introduces breaking changes every 12 months (which apparently used to be every 6 months-that must've been fun). "Breaking", i.e., lacking backward compatibility / inability to access new features from old code. Presumably one could theoretically continue to run the deprecated version; but it begs the question for how long that deprecated version would continue to receive support enough to be stable in production. Or is this just a reality of web frameworks in general; i.e. that one must be committed to rewriting / refactoring code on an annual basis? If I'm grokking this correctly, it seems to me that Laravel wouldn't be much different (in this regard) than the maintenance nightmare that has become the JS ecosystem. I value your insights. Peace.
If you update every year and follow the upgrade guide, its typically very minor changes that you can do in 10-30 minutes and they always backwards support the older structures so you don't need to do anything major.
The worst is the color theory of this ranking. D as green and S as red-ish. lol. Messed up. Thanks for the vdo though. Got a good look at the options I have for my project.
@@joshcirre Knew it this was that damn website. Dude, you see this ya? Absolutely upside down. I moved to Laravel from JS land as well btw. It's been 6 months and already delivering a client project. The things Laravel provides out-of-the-box is astronomical! Glad you are enjoying Laravel.
I have been searching for a sail-like docker-compose but for deployment. I mean, if sails can generate a docker-compose for us to work with Laravel locally, wouldn;t it be cool to have the same but for deployment? Like sails but with nginx/php-fpm instead of the php dev server... Right now, I just generate my sail project, copy all the docker-related stuff, then I add nginx/php-fpm on top of it. To make things even easier (but less performant), I store my cache, files and Scout servers all on the DB (using Mariadb). So one DB, one HTTP server and that's it. So, did you ever stumble upon something like sails but for prod?
While it's not an "official" package and I'm not a Docker master by any means, I would take a look at Spin by Server Side Up: github.com/serversideup/spin
![LAVROV's interview with Tucker CARLSON 😁 [Parody]](http://i.ytimg.com/vi/mbMemqc-QEk/mqdefault.jpg)
I appreciate your pragmatic approach to web development, embracing it as a typical developer. In our industry, there's a common tendency for everyone to claim expertise, and there's a misconception that complexity equates to superiority. I've personally experienced judgment from 'senior' developers for using a Git GUI client instead of the command line, so I can relate to this challenge. Ultimately, prioritizing tools that enhance coding efficiency and faster delivery is far more valuable than adhering to norms that might create unnecessary friction based on outdated perceptions of how 'real developers' operate.
Glad to hear you relate to me! I would say I’m a decent enough developer, but I still prefer when things are magical and easy instead of having to configure Docker or mess with a bunch of server settings.
Use the tools that help you become faster at building things. ☺️
I really love your channel, also js developer swicthed to Laravel. I'd appreciate if you'd put more content around these js developer transitioning like us, topics like PHP Crash course, Laravel Livewire serious, Creating Composer CLIs, Laravel project folder strucure and OOP, and more. Thanks bro.
This is helpful to know @abdu5822.
I’ll add them to the list! :) thanks for watching.
cir.re/suggest
I really appreciate your content, but as a devops and ex php developer, I would say learning Docker and taking the time to understand where and HOW your app runs, is as important as knowing how to write it. All those SaaS hide complexity away from you and on scale debugging becomes a nightmare. Not to mention vendor-lockin. A docker image is vendor agnostic, can be deployed everywhere and you got to tune it as a developer. Cheers.
Thank you for the support! ☺️
I definitely agree with you there. Even using Laravel Vapor, I still have a lot of flexibility using Docker to install extensions. I do think there’s benefit in finding solutions that allow you to get up and running with and without docker.
But I still have a lot to learn with Docker. ☺️
Fascinating insight into options out there for low friction deployment. I am intrigued by Bref and will subsequently look more into this - the idea of a Laravel app hosted as if twere a function and charged for when it is used and not for when it is not. Seems too good to be true but certainly worth the time to try it out. Thanks for all the tips, this is great.
I would recommend to anyone learning Docker at least if not containers in general and how to use these in a development life cycle. This leads into production delivery and as such is a good introduction to production concerns. It is like an 'interface' if you would to making your apps service ready and having consistent, repeatable and reliable environments from dev => prod.
I suppose I would say that, having learnt and used Linux since before y2k when it was slackware and on 20+ floppies but I'm on old curmudgeon i suppose. Ha ha !
Thanks for the insights and comments Jon!
I’ll admit that I wish I learned how to better use Docker earlier, and even with Laravel Vapor I still deploy using Docker to make use of a few extensions that aren’t available out of the box.
As someone who is still learning and only has experience pointing servers to a Git repo, your kind knowledge is exactly what more new developers need!
Have to learn how easy we have it before we learn how to make it easy.
@@joshcirre absolutely, thank you for your kind words
we are all still learning I think and if we are not we should be. I like you spent a lot of time in the Javascript SPA ecosystem and still do, thinking the old ways routed in Wordrpress and traditional CGI server based was no longer of relevance however PHP and Laravel have fresh approaches like livewire that challenge this thinking.
It is thanks to your comments and your channel I am now reviewing this and am looking to use Laravel for a use case we have right now, so thanks for your content and hard work and please do keep up doing what your doing. I've learnt a lot and certainly many others will too.
What are your thoughts on the objection to Laravel which I've stumbled across that its release cycle introduces breaking changes every 12 months (which apparently used to be every 6 months-that must've been fun). "Breaking", i.e., lacking backward compatibility / inability to access new features from old code. Presumably one could theoretically continue to run the deprecated version; but it begs the question for how long that deprecated version would continue to receive support enough to be stable in production. Or is this just a reality of web frameworks in general; i.e. that one must be committed to rewriting / refactoring code on an annual basis? If I'm grokking this correctly, it seems to me that Laravel wouldn't be much different (in this regard) than the maintenance nightmare that has become the JS ecosystem. I value your insights. Peace.
If you update every year and follow the upgrade guide, its typically very minor changes that you can do in 10-30 minutes and they always backwards support the older structures so you don't need to do anything major.
@@squarkyt Thanks brother. I'm keeping an eye on Laravel, but I've decided to begin my next dev journey with AstroJS.
The worst is the color theory of this ranking. D as green and S as red-ish. lol. Messed up. Thanks for the vdo though. Got a good look at the options I have for my project.
Don't blame me! I promise. 😂 That's just the tierlist maker website.
@@joshcirre Knew it this was that damn website. Dude, you see this ya? Absolutely upside down.
I moved to Laravel from JS land as well btw. It's been 6 months and already delivering a client project. The things Laravel provides out-of-the-box is astronomical!
Glad you are enjoying Laravel.
Love it! My favorite part about building with Laravel. 😊
I have been searching for a sail-like docker-compose but for deployment.
I mean, if sails can generate a docker-compose for us to work with Laravel locally, wouldn;t it be cool to have the same but for deployment? Like sails but with nginx/php-fpm instead of the php dev server...
Right now, I just generate my sail project, copy all the docker-related stuff, then I add nginx/php-fpm on top of it.
To make things even easier (but less performant), I store my cache, files and Scout servers all on the DB (using Mariadb).
So one DB, one HTTP server and that's it.
So, did you ever stumble upon something like sails but for prod?
While it's not an "official" package and I'm not a Docker master by any means, I would take a look at Spin by Server Side Up: github.com/serversideup/spin
@@joshcirre That sounds like what I'm searching for! Thank you!
Oh hi, guess you're in the bucket of other twitch streamers I am subscribed to 😊
Hey there Stoney_Eagle! I’m honored! :)