Go

Timeouts, connection reuse, response draining, and retry policy belong in the client design.

A good table captures behavior dimensions without hiding the arrange-act-assert story.

Parse once, validate completely, expose immutable typed configuration, and fail before serving traffic.

Small consumer-owned interfaces reduce coupling and make tests describe real dependencies.

Bound concurrency at the admission point so overload becomes visible and controllable.

Options help optional construction only when defaults, validation, and option interaction remain obvious.

A context is useful only when every blocking boundary observes it and cleanup has a clear owner.

Profile the constrained resource under representative load before changing code.

Correct cache synchronization must cover compound operations, expiry, and loader duplication.

Shutdown is a protocol: stop admission, drain in-flight work, flush state, then release dependencies.

A package is stable when its responsibilities, exported surface, and dependency direction are narrow.

Generics can remove unsafe casts while explicit synchronization and expiry semantics preserve correctness.

Allocation work starts with profiles and escape analysis, then targets lifetime and representation.

Child goroutines should share cancellation, error propagation, and a bounded lifetime with their parent.

Use channels for ownership transfer and coordination, not as a universal replacement for locks.

Every goroutine needs an exit condition that remains reachable when downstream work stops.

A pipeline without bounded queues and cancellation is an outage amplifier.

Choose receiver and parameter semantics from ownership, mutability, and copy cost rather than habit.

Benchmarks need stable inputs, allocation reporting, multiple runs, and a comparison tied to user impact.

Wrap errors for diagnosis, classify them for policy, and never make callers parse prose.