When writing code as a team, a common headache is “Who wrote this code?! 🤬” To minimize friction, it’s essential to have shared principles or team agreements on how to write code. Here are some simple tips that can make our lives better; please consider them.
The Go runtime has a few environment variables that can be configured, but there are two that DevOps folks often use as a starting point: GOMAXPROCS and GOMEMLIMIT. Let’s take a look at what each of them does.
When creating tables in a database, have you ever noticed why we have to choose the data size? Let’s take a look at how important column ordering is, using PGSQL as an example.
Software development methodologies are designed to help developers deliver code smoothly and with fewer defects. Recently, three terms have been frequently discussed: Domain Driven Design (DDD), Test Driven Development (TDD), and Behavior Driven Development (BDD). Although their names are similar, these methodologies have distinct differences. Here’s a comparison of DDD, TDD, and BDD from a lazy person’s perspective.
A common task when working with REST APIs is converting JSON back and forth between services. Typically, encoding/json is used, which is the standard library provided in Go. But now, there’s something new to try: goccy/go-json, which will make our services faster without any extra cost.
When writing Go, we often encounter situations where we need to read files or responses from API calls. Generally, io.ReadAll and io.Copy are used for this. This post will explore the differences between them.
