Performance
How to read a flame graph without guessing
Width is time, height is call depth, colour means nothing. A practical guide to reading CPU flame graphs from Go's pprof, using a real regression we fixed.
Site reliability engineer
Marek writes Go for the infrastructure side: proxies, workers and the retry logic in between. His posts cover profiling, backoff and what happens to a system when a dependency goes slow instead of down.
Width is time, height is call depth, colour means nothing. A practical guide to reading CPU flame graphs from Go's pprof, using a real regression we fixed.
Exponential backoff without jitter turns one outage into synchronized waves of retries. Here is a small Go helper that gets backoff, jitter and cancellation right.