Caching things can be hard to do and hard to test. In this post I’ll demonstrate a convenient way of doing that using interfaces.

I have written some exporters to observe things on GitHub. This is how and why.

Ever wanted to validate your Packer image with Goss? Well, you can!

I’m working in a project that uses Chef, so it has a lot of JSON files.

GoReleaser was able to build Snapcraft packages for a long time, but it wasn’t able to push them until today. Let’s see how to wrap to your TravisCI build!

I shared some of my experiences coding GoReleaser, this time, more about community and less about Go itself. Slides are more or less the same, but here they are anyway:

I have an old Couchbase 4.5.x cluster, and I though it would be nice to upgrade it. This are my notes and the tests I did before doing it “in production”™️.

A quick review of my second ever GopherCon - the first one as a speaker, and my experience talking.

Migrating an ElasticSearch cluster from version 2 to 5 can be challenging, even more if it is a big cluster.

I’ve started GoReleaser almost 2 years ago. This is a summary of (some) things I’ve learned down the road.

It has been one month since I started working fully remote, and I think I learned some things I can share.

I like to keep my GitHub clean. I delete forks I’m not using anymore, move old abandoned repositories to my graveyard and etc.

I wanted to set up a prometheus machine for me to monitor random stuff, but I was always postpone that because I didn’t want to use SSH port-forwarding, firewalls, create a VPC and/or setup an OpenVPN server or anything like that.

Everything in life eventually comes to an end, including life itself. This is not that kind of post, though.

When first announced GoReleaser roughly 1 year ago, on January 2017, I never thought it would be somewhat famous.

Over the years I read several articles on how to be effective, and how the 10x engineer thing is or is not a lie and all that.

After some time, I finally decided to move my blog from Jekyll to Hugo.

It was the Go 1.10 Release party - my talk was about what changed in Go 1.10.

I’ve been working on GoReleaser for more than a year now, and one of the things that was bothering me the most was fpm.

I spoke about how we migrate our monitoring infrastructure to Prometheus & Friends, what we got out of it and how it is working for us right now.

I showed how to build and release binaries in Go, including cross-compiling, Docker images, Linux packages and Homebrew, featuring GoReleaser on the end.

This past weekend I decided I need to clean up my GitHub profile. In this post I’ll write about why I cleaned everything up and also how I did, as well as some initial results.

I always wanted to know how stargazers of my repos increased over time.

I’ve been working with DigitalOcean, Heroku and AWS for some years now.

I’ve been using Jekyll on my blog since 2012. It is great! But, lately, its slow build times started to bother me.

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.

At ContaAzul, we have several old pieces of code that are still running in production. We are committed to gradually re-implement them in better ways.