What You Should Know Now — and What's Next

What You Should Know Now

• Core syntax: variables, zero values, control flow, slices, maps, functions, and multiple return values
• Structs, methods, pointers, and composition through embedding
• Interfaces, implicit satisfaction, and type switches
• Idiomatic error handling: returning, wrapping, and inspecting errors
• Generics with type parameters and constraints
• Concurrency with goroutines, channels, select, sync, and context
• The standard library for JSON, files, time, HTTP clients, and HTTP servers
• Testing, fuzzing, benchmarking, and profiling with the go tool
• How a production Go service is structured, secured, and deployed as a single static binary

What Should You Learn Next?

• Cloud-native tooling — Docker, Kubernetes, and Terraform are all written in Go; reading their source (or writing a Kubernetes operator) is a natural next step.
• gRPC and Protocol Buffers — a common way Go services talk to each other, building directly on the HTTP and concurrency lessons above.
• A related language — C if you want to understand the lower-level ideas Go's designers deliberately simplified, or Rust if you want systems-level control without a garbage collector.
• A web framework or router — the standard library is enough for most services, but libraries such as chi or Echo are worth knowing when you join an existing codebase that uses them.

Build Something

Pick a project idea that solves an actual problem you personally have — and build it as a small Go command-line tool or HTTP service, with table-driven tests alongside it from the start and go test -race in your routine.