From many reasons I was always using  SQL_CALC_FOUND_ROWS to get total number of records, when I was running limited query. Never especially thought about it, until i had some super performance issues with one of my projects. Obviously after quick profiling and googling  i found people complaining about FOUND_ROWS() low performance . I was not aware how big impact it was until I tested.

From time to time we could breach  max_input_vars restriction. Which basically limitation for server which allows only limited number of input server to reach out server. Usually this number is around 1000. In this short tutorial I will describe, how to easily avoid this problem.

That one was tricky. Got brand-new router and couldn’t connect to 5 Ghz network. My iPhone didn’t have this issues, neither couple other devices at home. I spend some time randomly changing settings on wireless network, and then I found tricky information – my MacBook can’t use all available channels, can work only on specific one.

PHP 7.0 it’s already a while on the market. Let’s install it on EC2 instance.  Here you can find a quick recipe:

I’m huge fan of Continuous Integration and all possible automation which can save me any time during development process. I’m using plenty of different tools in my daily work, but there is always place for something new.

Basically each decent IDE has FTP client build in, but sometimes you don’t have access to your IDE but obviously you got your code in GIT repository. If you are using Bitbucket or Github you are lucky – you can use FTPloy  . It’s super simple service, which gives you option to bind your repository with FTP server. After change is made – it deploys your files on the server. Nothing more, nothing less.