Build a tiny `main.go` file with `package main`, an import, and `func main`. You’ll trace why this specific shape makes a file runnable as a command-line program without diving into functions yet.

Run your program with `go run .` and connect the command to what happens behind the scenes: Go finds the package, compiles it, runs it, and reports errors if the source is not valid.

Use what you learned in the previous lesson to solve real-world problems.

Compare `go run` with `go build` so you know when you want a quick execution versus a saved executable file. You’ll identify the output file and run it directly from your terminal.

Use what you learned in the previous lesson to solve real-world problems.

Check what you understood with a short quiz.

Read how Go groups source files by folder and `package` line. You’ll recognize why a runnable program needs `package main`, and why files in the same folder usually share the same package name.

Use what you learned in the previous lesson to solve real-world problems.

Use `gofmt` and `go fmt` to rewrite code into standard Go style automatically. You’ll practice formatting one file or a whole module and see why Go projects avoid custom style debates.

Use common `go` command patterns like `go help`, `go env`, and `go list` to inspect your setup and project. You’ll know which command answers “what is installed?”, “what is this package?”, and “where can I get help?”

Check what you understood with a short quiz.

Review this chapter with practice based on your mistakes.