Refactoring real-world Laravel app. Who wrote THIS CODE?!

I live for the clickbait.
In this video we'll focus on refactoring a Laravel application using the 80/20 rule. We'll just go through the files, see what we can do to improve the code slightly without stressing over the details.
More me:
saaslaravel.com

[@user-zh2oz9fe4m]

It's a very useful video! Looking forward to seeing more of these)

[@limitlesskode]

The refactor when you delegated the user service instantiation to laravel was quite cool. I was manually creating these instantiations in the constructor body and I think I will refactor to your approach.

[@natenatters]

I really like the refactoring videos! Nice job. Good to aim for the 80/20 rule too, you seem to get a lot of work done quickly!

[@saaslaravel]

Thank you Nathan! I'm learning Vim so maybe I'll be able to push that speed even further 😊

[@natenatters]

@@saaslaravel Oh no 😆Im happy to watch you work in Vim, but I refuse to learn it as an IDE haha

[@saaslaravel]

@@natenatters It's def challenging but that's what makes it fun haha :D

[@gotoslovakia]

Great job. Thank you

[@akhileshkumar-iu9uq]

Can u name the vscode extension which make ur code very real

[@karlson2804]

Very, very cool format, if possible, shoot more, please.

[@mohammadashrafuddinferdous9347]

At 8:24, UserService isn't the appropriate service class. It should be user order service if there are any other type of order services. Otherwise, user service will be a god service, sooner or later.
And i think usrr service should always return user objects. It can be user model or dto or the collection of dto or user models. But when it returns anything else, it breaks the law of diameter.

[@saaslaravel]

This project isn't super complicated and doesn't have loads of code, but if I was working on something more complex, I agree that UserOrderService is better

[@mohammadashrafuddinferdous9347]

@Przemysław Przyłucki Surely, if it's not complicated and only one person is working on it, then the path is ok to me too.

[@mohammadashrafuddinferdous9347]

@@saaslaravel I like you super simple dto btw.

[@_bijaydas]

I see you have a few Enums. What is preferred storing statuses for products, users etc. in Enums or in a table? I used to use Enums but now converted all status to status table.

[@saaslaravel]

I use enums that cast to an int and just save the int in the db. This way I have nice type hinting in the app layer and can add more enums without having to alter db

[@SilverPaladin]

@@saaslaravel I saw your Enum approach in another video and I love it! I hate having to touch the db to add or change the enums! I guess we could also add a layer on top of that for different languages?

[@GergelyCsermely]

Thanks

[@binaryfire]

Great video! What are your thoughts on actions vs services?

[@saaslaravel]

I use actions as well - mostly when there a piece of logic that needs to be reused between different parts of the system, or when a service method has to interact with a 3rd party

[@2gbeh]

When to use Actions and when to use Traits ?

[@carvalho1990]

Is there a repo for this code? Amazing! thanks!

[@saaslaravel]

Unfortunately not, that's a private project

[@Nodsaibot]

ANY php project that it requires use of the CLI means you are doing things WRONG, PHP was not created for this use environment

[@SunilYadav-tm6kt]

Not at all, its depends on requirement and use case