Go

Go beneath the surface — goroutines and the scheduler, channels and CSP, interfaces, the GC, and the language's deliberate simplicity.

Go's governance and proposal pipeline, the Go 1 compatibility promise, release cadence, and the community organs around them.

The house hexagonal reference realized for Go — one Go module per service, a modulith of facade-fronted context packages under internal/modules/, cmd/ binaries as assemblies, ports at the consumer, nested internal/ walls that make the gateway rule a compile error, and explicit constructor wiring with wire as the sanctioned escalation.

The single go command as the entire build system — distribution, environment, and the catalog of built-in and companion tools.

The Go specification versus its implementations — the gc reference toolchain, gccgo, gollvm, TinyGo — and the WASM targets.

Go's single first-party build path — the go command plus modules — and the artifact formats and module ecosystem around it.

How Go's stdlib-first web culture shapes the field — net/http, thin routers like chi, full frameworks Gin and Echo, and the fasthttp outlier Fiber.

Map of Go testing strategies — unit to security — with the stdlib-based tools for each and links to the deep-dive notes.

How REST, GraphQL, gRPC, WebSockets/SSE and messaging map onto Go's stdlib and the dominant community libraries.

How Go reaches every storage kind — database/sql, per-store drivers, and the raw-driver-to-ORM spectrum, mapped store by store.

How the recurring security concerns map onto Go's stdlib and de-facto libraries, composed as middleware rather than a framework.

Practice material: katas, challenges, build projects.