Don't Panic — Go Fundamentals

Go is a compiled programming language that arrives with a unusually complete set of tools and an opinion about how a project is arranged. A module contains packages, packages contain source files, and the go command keeps the whole arrangement from turning into a drawer of cables. That is already more useful than it sounds.

Start with the module: a versioned collection of related packages rooted at go.mod. A package is the smaller unit that compiles together. An executable is merely the package named main with a main function, which is Go's quiet way of saying that programs ought to announce where they begin. Names beginning with uppercase letters cross package boundaries; lower-case names stay private. The language has no class inheritance waiting behind a curtain. It prefers structs, methods, and small interfaces that describe behavior.

The first surprise is that Go gives every variable a zero value. Numbers begin at zero, strings begin empty, and several useful-looking things begin as nil. This is convenient until a nil map receives a write and objects on principle. Slices are similarly sociable: two slices can share underlying storage, so a change through one can appear through another. The compact syntax does not remove the need to know who owns a value.

Then comes concurrency, where Go is cheerful enough to hand you goroutines and channels before asking whether any of them know when to stop. A goroutine runs concurrently. A channel carries typed values between goroutines. Neither makes shared mutable data safe, and neither cancels work by magic. Define ownership, cancellation, and completion before adding the clever part. The race detector is a useful alarm, not a substitute for a plan.

Errors are values, so handle them where there is context to add or a decision to make. defer schedules cleanup when a function returns, which keeps successful acquisition and cleanup near each other. The daily ritual is refreshingly plain: format, test, inspect, build. go mod tidy keeps dependency requirements aligned with imports, because even tidy languages have paperwork.

Read the intro for the full map of types, packages, interfaces, and concurrency. Use the slides when the relationships need to fit on one screen. Keep the cheatsheet beside a small module while the commands and zero values are still unfamiliar. The reference path then leads from the Tour to the specification, where the precise rules wait patiently and without sympathy.

Don't Panic — Go Fundamentals

Relevant careers