List of lectures for the course Go, 72 quest level on JavaRush

Demo‑scenario: how to showcase CLI/HTTP functionality in 5–10 minutes
Go SELF
72 level,0 lecture
A practical cheat sheet on how to demo a project with CLI and HTTP API in 5–10 minutes so the listener sees the value: first the behavior (commands and requests), then the contracts ( stdout/ stderr, exit codes, HTTP statuses, a single error envelope), and at the end — quality signals ( go test, stable output, no leakage of internal errors, X-Request-ID).
Open
Common Go interview questions
Go SELF
72 level,1 lecture
We break down popular Go questions that come up most often in interviews: how to explain code behavior via the execution model, how errors work (why error is an interface, why %w exists, how errors.Is/ errors.As work), where interfaces break because of typed nil, what matters about slices (backing array, aliasing, append), and how to answer concurrency questions (goroutine, channels, WaitGroup, deadlock, and data race).
Open
What to learn next: SQL/DB, Docker, CI, profiling, security
Go SELF
72 level,2 lecture
We move from “I know Go” to “I can build a product”: how to grow a project around Go code through storage (SQL/DB), reproducible packaging and execution ( Docker), automated checks ( CI), performance measurement ( pprof/benchmarks/traces), and basic operational security (limits, secrets, errors). All using the example training project Tasker.
Open
Go ecosystem: popular third-party libraries
Go SELF
72 level,3 lecture
We break down a “map” of the Go ecosystem: what most tasks are covered by the standard library (HTTP via net/http, JSON via encoding/json, tests via testing, structured logs via log/slog), when it makes sense to reach for external dependencies, how to calculate the cost of dependencies (direct/transitive modules, go.mod/ go.sum, updates and CVEs), how to choose a library based on requirements, and how to plug it in carefully—via adapters—so that the domain and use cases do not “leak” dependencies.
Open
Personal growth strategy: portfolio, code review, and reading the stdlib
Go SELF
72 level,4 lecture
How to build a clear and “trustworthy” growth path in Go: make a portfolio not about the number of repositories, but about contracts and reproducibility; turn README into the project’s interface; level up your review skill through self-review and small, testable changes; read stdlib sources (for example, io, errors, net/http) in small chunks; and maintain a sustainable weekly cadence with measurable steps.
Open