Loading…
0+ curated questions with the same answer shape every time: quick recap, deep dive, pitfalls, and follow-ups. Coverage includes .
Go modules are the standard for dependency management since Go 1.11, and the toolchain questions come up in every seniority-calibration round. This module covers the go.mod file (module path, Go version directive, require and indirect dependencies), go.sum (the cryptographic hash of every dependency version — why it's committed and what happens if it's missing), go get and go mod tidy (why tidy removes unused dependencies and how it affects go.sum), go work and multi-module workspaces (the Go 1.18+ feature for local development across multiple modules in a monorepo), replace directives (local replacement of a dependency — the pattern for forking a library, and why you must remove the replace before tagging a release), vendoring with go mod vendor (the trade-off between reproducibility and repository size), and go generate (the tool directive convention for running code generators — protoc, mockgen, sqlc, stringer). The interview question: 'how do you safely upgrade a transitive dependency in Go?'
Full catalog
Topics are ordered for learning. Within each topic, rows are numbered 1–0 globally so you always know where you are. Collapse topics if you want a lighter view — use Expand all when you need the full list again.
Numbers 1–0 follow the order we recommend — click any row to open the full answer, or use the sticky Next link at the bottom of each page to go Q1 → Q0.