You could try examining the parts of the standard library used in your own (test) apps, and how they relate, to get a top-to-bottom view. Or start with smaller

You could try examining the parts of the standard library used in your own (test) apps, and how they relate, to get a top-to-bottom view. Or start with smaller/less interdependent packages, if the larger ones seem too complicated at the beginning (just browse until you find ones that seem grokkable). Maybe look at stuff like input/output param patterns, naming (terse!), composition, etc. Ha, "pointers": https://groups.google.com/d/topic/golang-nuts/H7LrVJhXyv4/discussion https://groups.google.com/d/topic/golang-nuts/H7LrVJhXyv4/di... https://groups.google.com/d/topic/golang-nuts/x-huAZm8yP0/discussion https://groups.google.com/d/topic/golang-nuts/x-huAZm8yP0/di... https://groups.google.com/d/topic/golang-nuts/EfLHIHFNsjA/discussion https://groups.google.com/d/topic/golang-nuts/EfLHIHFNsjA/di...