Laravel Horizon is a fantastic tool, which I use in all my projects for my queues. If you are using Horizon, I’m sure you’ve noticed that there are 2 separate places for the failed jobs: in database `failed_jobs_table` and and in Redis. …

If you are tinkering with a big data (say are trying to export a huge CSV), you may end up needing to query +100k ids in a whereIn(). And if you try it to use +100k ids in a whereIn(), you’ll see a MySQL error “General error: 1390 Prepared statement…

There are bunch of ways you receive Laravel errors in front-end and inside your ajax request, you need to parse and display the errors nicely. Inside blade, it’s pretty easy to handle and display errors but inside javascript? In my projects, I realised a pattern that I was repeating myself…

As a rule of thumb, we should never run database queries inside a for-loop! “Database transaction” is an expensive operation. For example, let’s say we designed an inventory software and it’s being used in production for a year, and reached 1,000,000 transactions. Suddenly, we learnt that we didn’t add the…

When a user took an action, we all love to show them a success message or error message. I actually like to use sweet-alert as it looks professional. Wouldn’t it be cool if we could simply write in our controllers: $this->flashSuccess("Task was successful!"); $this->flashError("Task failed!"); …don’t actually need to do…