Go turns 17, and the err != nil debate flares up again

Go hit its 17th birthday, which prompted the usual round of looking back and forward. Fittingly, the day's liveliest thread picks at the oldest sore spot in the language, arguing that the ever-present err != nil checks are a DRY violation nobody wants to admit to. Elsewhere, a couple of short videos take aim at two things most Go services get subtly wrong: stuffing context.Context into structs, and shutdowns that return from ListenAndServe and promptly cut in-flight requests off at the knees.