Stuck to this programming quote since my first line of code.

Append this middleware to your applications and 10x your debugging. Anything that originated from this request will carry the context along, e.g. Jobs, Logs. For jobs especially, you can even grab the user that triggered the job from within the job itself.

Everything is CRUD!

RT @_newtonjob: @Davi_g117 @enunomaduro I love actions. They are a different name for the command bus pattern which Laravel's Command Bus s….

RT @PovilasKorop: So simple. So smart.

Need an admin panel? Try Tableplus.

I do this on most projects. Thank me later. 🙂

Please don't tell me people genuinely do pre-commit hooks. 🥹. I can throw away my machine if I have to wait 1ms to do a commit or push.

Laravel's job batching is soooo good! 🤦‍♂️.

RT @sumfreelancer: Stuff like this, I am in twitter for. @_newtonjob.

People often create a whole new middleware class just to handle some global authorization. In many cases, you can still take advantage of Laravel's built-in Authorize middleware. Here's an example 👇

If you're performing other database operations from observers or listeners when a model is being saved, you may want to wrap the entire operation within a database transaction to ensure consistency. 🔄. updateOrFail(), saveOrFail(), deleteOrFail(), etc. are nice helpers for that.

Any class can be made `UrlRoutable` and benefit from implicit route bounding. In this example, I've extended the Carbon class to implement the `UrlRoutable` interface so that I can inject any date route parameters directly as a Carbon instance.

Also, note that if you MUST version your API at some point, you can still start without versioning. GET /api/users <--- This is v1. GET /api/v2/users <--- This is v2 (which mostimes never happens).

Link to the original post.

Mostly agree with other points in this post, but. IMO, it is rather bad practice to version your APIs from the start. This already gives the impression that you intend to break it in the future. APIs can evolve with new properties without breaking existing client integrations.

I was already on my way to implementing a custom helper to wrap sentences without spoiling words. Then I found the helper I was looking for. Str::wordWrap() 😍

RT @_newtonjob: @MrOluwatobby @enunomaduro @dhh Cool thing is, Laravel long introduced the Action pattern a.k.a "Command Bus" in 5.x, which….

RT @PovilasKorop: Yes, for many projects, that is enough. I have a separate video about WHEN to choose spatie/laravel-permission package,….

You're probably going overly complex with roles and permissions. For the majority of apps out there, Laravel's built-in authorization just works. 🤌

How many queries at most do you expect to run on a single page? How much is too much?