Learning Go An Idiomatic Approach to Real-World Go Programming (Jon Bodner [Jon Bodner])（Z-Library）

【One-Line Pitch】 A practical, opinionated guide to writing Go that looks like Go—not Java or Python translated into Go syntax. Best for developers who already know another language and want to become immediately productive and idiomatic in Go, from setup through concurrency, testing, and real-world tooling. 【Book Arc】 - **Opening (~0%–10%)**: Frames the book's core thesis—Go is deliberately "boring" and small, and idiomatic Go requires understanding how its limited features fit together rather than importing habits from other languages. - **Early (~10%–35%)**: Sets up the development environment and toolchain: installing Go, understanding the workspace and GOPATH, and the difference between `go run` and `go build`, plus installing third-party tools via `go install`. - **Middle (~35%–55%)**: Moves into tooling discipline—`go fmt`, `goimports`, the semicolon insertion rule, linting with `golint`, and vetting—showing how Go enforces style and catches mistakes before they reach production. - **Late (~55%–85%)**: (Excerpts do not cover this stage in detail.) Based on the book's stated scope, this is where core language material—variables, types, control structures, functions, and eventually concurrency—is developed in depth. - **Ending (~85%–100%)**: (Excerpts do not cover this stage.) Presumably closes with advanced and real-world topics such as concurrency patterns, testing, and HTTP server work, though the provided excerpts stop before these. 【Key Takeaways】 - **Idiomatic Go is the real subject, not just syntax** (Opening): The book's goal is code that "looks like Go," which means resisting the temptation to write Java- or Python-shaped programs in Go. - **Go's small feature set is a design choice, not a limitation** (Opening): No inheritance, generics (at the time), exceptions, or operator overloading—"boring" is intentional and supports maintainability. - **Don't skip the fundamentals** (Early): The author explicitly warns that seemingly obvious material on variables, types, control structures, and functions contains the details that make code idiomatic. - **Tooling enforces style automatically** (Middle): `go fmt` and `goimports` reformat code, and the semicolon insertion rule explains why brace placement matters—run them before compiling. - **Linting is advisory but culturally important** (Middle): `golint` suggestions aren't compiler errors, but ignoring them makes your code "stick out" to Go developers. - **The workspace model has changed and old advice is obsolete** (Early): Modern Go lets you organize projects freely; GOPATH mainly matters for third-party tools installed via `go install`. - **`go run` vs. `go build` reflects intent** (Early): Use `go run` for scripting-like experimentation and `go build` (with `-o`) for distributable binaries. - **Go shares code via repositories, not a central registry** (Middle): `go install` pulls from source repos (e.g., GitHub) with version suffixes like `@latest`, unlike Maven Central or NPM. 【Reading Tips】 - **Deep-read the early chapters even if they feel basic.** The author explicitly says the idiomatic details live here; skimming risks absorbing non-Go habits. - **Skim the installation and O'Reilly boilerplate** (roughly the first quarter) if your environment is already set up—focus instead on the workspace and tooling concepts. - **Treat the tooling chapter as a checklist.** Actually run `go fmt`, `goimports`, and `golint` on a small project to internalize the workflow. - **Keep Effective Go and the Code Review Comments wiki open** alongside the book, as the author recommends them for understanding idiomatic style. - **Use the GitHub examples and Go Playground** to run code as you read; the book assumes you'll experiment. 【Coverage Limits】 The provided excerpts cover only the preface, setup, and tooling portions of the book (roughly the first half). Core language chapters, concurrency, testing, and HTTP material are referenced in the book's stated scope but not detailed in these excerpts, so this guide cannot summarize their specific content.