howtogo.dev
A reference and learning system for Go 1.26. Every example on the site is a program that was run before it was published, and the output beside it is what it actually printed.
It is organized by what you arrived wanting to do, which is why the same subject can appear in more than one place. Reading about slices and reaching for the one line that copies a file are different jobs.
The five doors
Who writes this
Keith Thomson, a software developer in southeastern Connecticut. He builds and maintains training systems for a company that trains United States Navy submarine crews, works mostly in Go, Rust and Python, and runs WhaleLogic. He holds a degree in computer science and served in the Army.
How to Go started because the Go documentation he wanted did not exist. The official docs are precise and assume you already know why you are reading them; most tutorials are the opposite. This site tries for the middle: short pages, real programs, and enough plain English around them to explain why the code is shaped the way it is.
It is open source. If something here is wrong, or a page would be better with an example you have written, the repository takes issues and pull requests.
