Understanding the Go Runtime: Profiling
Jesús Espino makes Go profiling feel less like a magical command-line ritual and more like five concrete collection systems. The useful distinction is not just CPU versus heap: CPU samples arrive through a signal-driven stream, heap/block/mutex profiles aggregate at the event site, and goroutine profiles are a deliberate snapshot. Once that machinery is visible, the profiles are easier to choose and their numbers are harder to misread.
There is also a worthwhile standard hiding behind the Hacker News conversation about the post's unusually polished cadence: internals writing earns trust by being inspectable. This piece meets that bar with runtime-source references and a clear accounting of what gets sampled, buffered, aggregated, and estimated. For performance work, that provenance matters as much as the final flame graph.