Golang

Introduction After we set ourselves the goal of system reliability, our first goal must be awareness.  Simply put, we must be fully aware of how...

For those of you like me who Go is not the first language you learned, you might be familiar with "Enums" or "Enumerated Types". While Go does not have an enum per-say you can achieve...

Last week I was privileged to give a talk to the Singapore Gophers meet up held at the GrabTaxi Singapore Tech Office. The talk was titled "Dependency Injecting (and Testing)" and was inspired by this great article...

After way too long, I finally had the itch to blog again.  Firstly, sorry about the hiatus. As those of you that follow me on Linkedin know, in February I joined my very good friend Aaron...

The following content is a small extract from my latest book Beyond Effective Go – Part 1 – Achieving High-Performance Code. Slow consumers When designing function...

Friends & fellow coders, I am overjoyed to share that part 2 has finally arrived. In this book, I share my secrets to writing high-quality Go code efficiently, effectively, and productively. It contains practical approaches to software engineering, software design, and code UX that will set you on the path to success. As you may know, in part 1, we focused on making our applications faster; part 2 focuses on making the programmer faster. As the DORA study has shown, writing high-quality code is key to delivering software quickly. For others, please pick up your copy of the book at your local Amazon website or your preferred bookstore.

In the previous post, we examined the Why and When of testing in this post, we will build on that foundation and look at How much we should be testing.

In the previous posts, we examined the Why, When, and How Much of testing. In this post, we will complete the thread with an examination of What we should be testing and What we should not be testing.

Have you ever added a new feature only to have another one break?  After fixing the break, something else breaks, like some kind of bug whack-a-mole? Have you ever...

Introduction In Part 1 of this series, we introduced the goal of understanding how our system performs by adding instrumentation. This article expands on this goal by taking...