In this post, I’ll explain why I consider that increasing your Time To First Byte (TTFB) is the right thing to do.

A few months ago, I decided to move away from Google Chrome and gave Mozilla Firefox another chance. I’ve been happy with it so far, except for an annoying bug that I encounter all the time and which is the subject of this post. The weird part is I couldn’t find anyone reporting the same bug lately, so it might be due to my configuration (or my inability to use Firefox properly!). I know some Hunter customers encountered it as well. Though, I feel it deserves a post, so I can at least ping @firefox :)

Heroku is a amazing Platform as a Service that enables you to build and run application in the cloud. It’s often the first choice for deploying an app when you don’t want to focus on something else that the app itself.

I’m sure it happened to you, more than once: you run a command on a remote host, thinking it will finish in a few seconds. Unfortunately, after 5 minutes looking at your terminal and hoping for the command to be done soon, you realize that it will take hours. Obviously, it’s Friday afternoon and you had planned a trip for the weekend.

I (painfully) discovered a few weeks ago why specifying how much CPU and RAM a container needs was so important on Kubernetes. In this post, I will explain why ;)