Yisrael Dov :emacs: :nixos: on Nostr: nprofile1q…xmmpy I don't think that any one is a "Laravel" programmer ... it is a ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq5tepx7lk826fa82s683nqw85lte8mn8e2ujg2gvxavkvxl9asx9qsxmmpy (nprofile…mmpy) I don't think that any one is a "Laravel" programmer ... it is a tool. (unless you are on the laravel dev team)
It is a tool though that encourages bad programming.
From the laravel documentation "Generally, most of your tests should be feature tests. "
What kind of trash is that?! Shows a lack of understanding of TDD!?
While you *can* do things correctly. IoC etc, it is not made clear by the documentation.
Take a look at the doc for database (https://laravel.com/docs/11.x/database#running-a-select-query)
Why are they showing you to do a query in side a controller!?
Also the example code is littered with "Facades" ( to the average programmer, static classes ).
This kind of code is what makes people think that #PHP is a garbage language.
It is a tool though that encourages bad programming.
From the laravel documentation "Generally, most of your tests should be feature tests. "
What kind of trash is that?! Shows a lack of understanding of TDD!?
While you *can* do things correctly. IoC etc, it is not made clear by the documentation.
Take a look at the doc for database (https://laravel.com/docs/11.x/database#running-a-select-query)
Why are they showing you to do a query in side a controller!?
Also the example code is littered with "Facades" ( to the average programmer, static classes ).
This kind of code is what makes people think that #PHP is a garbage language.