I’ve been using Jekyll on my blog since 2012. It is great! But, lately, its slow build times started to bother me. I consider moving to Hugo, but that seemed like a lot of work, and I didn’t know what the real problem was. In this post I’ll show how I improved my Jekyll blog build time in about 75%.
We are running Kubernetes on both sandbox and production for some months now. Our production cluster is still small, with few services running on it, but, most of our sandbox environment is running on a Kubernetes cluster on AWS.
Last few months I’ve been using Go to write quite a lot of tools. In this post I intent to show not why I chose Go over others, but how I architect those tools, what libraries I use and what kind of automation I have in place.
Microservices is the new fancy way of doing applications. Yet, most companies still have big and old monoliths in production. In fast evolving software of this size, it’s usual to have lines of code which are never executed in production. Production code coverage reports can help us find those lines.
At ContaAzul, we use the CI infrastructure a lot. We open
several pull requests in several projects every day, and we block the merge
until the build pass. We consider our master branches are sacred, and
we can’t afford too much waiting to change them.