Reflected Go by node

A JSON unmarshaller drops a field on the floor and the bug ships to production. One typo in a struct tag did it. The standard library cannot warn about that, because the work happens at runtime, through the reflect package. This book is for the Go developer who has used encoding/json, hit a stack trace that claimed a field did not exist, and wanted to know what was actually going on. Five chapters: reflect.Type and reflect.Value, walking structs and reading tags, calling methods and building values at runtime, and the case for reaching past reflection entirely now that generics and code generation exist. Every listing runs in the CivNode browser sandbox. No Docker, no third-party imports. Reach for reflection last, not first.