time.Time is the perfect choice for handling times in Go in most cases, it even comes in the standard library!
Go is a strongly typed language, which means at any point a developer should know exactly what type of value they are dealing with.
I’ve often seen, and have been responsible for, throwing code into packages without much thought. I’ve quickly drawn a line in the sand and started putting code into different folders (which in Go are different packages by definition) just for the sake of findability.
Golang is King when it comes to concurrency. No other language has so many tools right out of the box, and one of those tools is the standard library’s sync.
Interfaces in Go allow us to treat different types as the same data type temporarily because both types implement the same kind of behavior.
Errors in Go are a hot topic. Many newcomers to the language immediately level their first criticism, “errors in go are clunky!
Go is becoming very popular for backend web development, and JWT’s are one of the most popular ways to handle authentication on API requests.
I’m going to focus mostly on some design decisions and also how I went about writing an SPI interface using Go on a Raspberry Pi.
Let’s discuss a few rules of thumb for logging in Go, as well as some features you may not have heard of that can make debugging easier.
The quick answer is that Go does not support constant arrays, maps or slices. However, there are some great workarounds.
Go has become increasingly popular in recent years, especially in my local area. It has been consistently displacing other backend languages like Ruby, Python, C# and Java.