It is an accepted wisdom that it’s more important to write code that is easily read and understood, in contrast to writing code that is fast to write1. This is typically used in discussions around verbose or statically typed languages versus terser dynamically typed languages. The kernel of the argument is that it doesn’t take you that much long to write a longer method name, spell out a variable in full, or import a class. Wheres it can take someone...| willhbr.net
Passionate programmer, experienced Extreme Programmer, Senior Agile Software Engineer, remote worker from Spain, Open Source enthusiast, and avid learner with a focus on software craftsmanship, and IT security.| Domenico Luciani - How to use generics to avoid duplications and make your co...
Go 1.18 adds generics, native fuzzing, workspace mode, performance improvements, and more.| go.dev
Documentation| go.dev
One of the things I enjoy about Go is its standard library, which comes with batteries included. Sure, some packages (like flag) aren’t as powerful or ergonomic as the available alternatives but I’m generally willing to accept this in order to avoid dependencies. Testing The same also applies to Go’s built-in test support, the testing package. Let’s look at a typical test: package example import "testing" func Add(a, b int) int { return a + b } func TestAdd(t *testing.| citizen428.net
