GopherSRE

A little about TLS use in gRPC When you look at most examples for gRPC client and server, there are two examples given: Set grpc.WithInsecure for the client, turning off TLS Create a self-signed certificate for the server and supply the public cert to the client Both of these are bad practices. WithInsecure just says: "Hey! Please man in the middle me". There are plenty of websites [Read More]

Introduction It is my contention that naked regular expression use (regexes) within SRE and DevOps software and tooling provides for: Hard to read code Difficult to reason when errors occur Bad matches that are assumed to be good data Causing outages or unintentional consequences in tooling It is not the contention that regexes are bad in nature, but that their ease of use combined with abilities to match large and [Read More]

Today I am announcing a Go Language Basics class. The class is provided as a free video and accompanying class materials in PDF format. The class is meant to bring new programmers up to speed with Go. It is heavy on exercises and because its video, it provides animated illustrations of slice internals, pointers, ... This class provides similar materials to what I taught at Google and Microsoft around the globe. [Read More]

What the worst projects say! [Read More]

Sooner or later every Go programmer will want to extract an object from another object such as Context or utilize an object that can be set to nil throughout the call stack. However, this can lead to ugly code that looks like: func someFunc(obj *MyObj) { if obj != nil { DoThis() } otherFunc(obj) } func otherFunc(obj *MyObj) { if obj != nil { DoThis() } ... } I this case, if our obj != nil, we want to [Read More]