Posts

An SLO connects user-visible success to an error budget and concrete release decisions.

A cursor must encode a stable total ordering, not merely an offset into changing rows.

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

Startup, readiness, and liveness answer different questions and should trigger different actions.

Building a simple bank API in Go using gin, gRPC, and sqlc

Guide to installing Go and running your first program

Starting YouTube to grow and find my path

Managing Linux services and boot with systemd