GopherCon 2020: Working with Errors - Jonathan Amsterdam
Go 1.13 introduced support for working with wrapped errors, in the form of three new functions and a new formatting directive. But those small changes have big ramifications for how you return errors from your code, and how you act on errors from the code you call. Jonathan's talk begins by defining what it means to wrap errors, and when you’d want to do so (and when not!). He'll then explain how the additions to the errors and fmt packages support wrapping. Jonathan will also address some features that didn't make it in, like stack traces and formatting. He will show how you can incorporate those features, and others like error codes, into your own error packages.

▶︎
GopherCon 2020: Go is Boring... And That's Fantastic! - Jonathan Bodner

▶︎
Gopherfest 2015 | Go Proverbs with Rob Pike

▶︎
Structured Logging for the Standard Library - Jonathan Amsterdam

▶︎
Understanding Allocations: the Stack and the Heap - GopherCon SG 2019

▶︎
5 Levels of Go Error Handling

▶︎
GoRoutines and Error Handling: Essential Techniques for Software Engineers

▶︎
Golang UK Conference 2017 | Arne Claus - Concurrency Patterns in Go

▶︎
The secret to making Golang error handling a breeze

▶︎
Go Class: 32 Error Handling

▶︎
GopherCon 2017: Go Anti-Patterns - Edward Muller

▶︎
GopherCon 2019: Handling Go Errors - Marwan Sulaiman

▶︎
Go flag Module - Reading Command-Line Flags in Golang!

▶︎
GopherCon Europe 2020: Raphael 'kena' Poss - Error Handling and Pitfalls in Distributed Go Apps

▶︎
GopherCon 2016: Don't Just Check Errors Handle Them Gracefully - Dave Cheney

▶︎
Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker

▶︎
justforfunc #9: The Context Package

▶︎
7 common mistakes in Go and when to avoid them by Steve Francia (Docker)

▶︎
Conan O’Brien Mocks Trump At Harvard Commencement | Crowd Erupts During Viral Speech

▶︎
GopherCon 2022: Exploring Network Programming by Building a Toxiproxy Clone - Jordan Neufeld

▶︎
