In this second part of the Linux troubleshooting series we’ll take a closer look at how to debug memory issues on Linux servers. Getting an overview To quickly see the current memory usage, you’d run the free command. …

In this article we’ll be walking through a few things to do when debugging CPU issues on a Linux server. We’ll be walking through a few standard tools available on (almost) all Linux machines that can help you figuring out the root cause. To start with, if you don’t know…

Introduction I’ve been using the table based tests pattern in Go for a long time and it has served my purposes well. We are also using it extensively at Saltside. A common code review comment I give is to use the sub test pattern in Go. …

Every now and then I find developers struggling with handling time in their tests, so I wanted to address that in this blog post. Typically there would be code that looks something like the below that needs to be tested: import ( "fmt" "time" ) func WhatTimeIsIt() string {…

I’m getting questions quite often about how my neovim is configured for Go development. So in this article I intend to describe just that. In the interest of brevity I’ll not cover the setup in general, but rather the Go parts in particular. My setup is based on neovim. Most…

Overview We all use a lot of packages when constructing our applications, both internally developed and third party packages. This blog post will show how you can easily mock these packages using mockery and stretchr/testify/mock. Let’s dive into it; An example When writing unit tests for our code we might find the external packages problematic. …

What should I test? What you need to test in Go is really not much different from any other programming language. Except maybe that you need to take extra care with pointers if you are not coming from that background. Generally I advocate testing on all levels. Which in practice only means that you…

I the early days of my programming career I didn’t really see the value and mainly thought it duplicated work. Now however I usually aim for 90-100% test coverage on everything I write. …

This is the first article in a series of lessons I’ve learnt over the couple years I’ve worked with Go in production. …