Your Go service is slow, but you don’t know where. Guessing is not a strategy. pprof tells you exactly where your program spends its time, memory, and CPU; here’s how to use it.

Before picking REST, gRPC, or Kafka, you need to answer a more basic question: does this interaction block, and does the caller expect an answer? Get that wrong and no technology choice saves you.

Before you draw a single service boundary, you need a vocabulary for why some splits age well and others turn into a distributed monolith. Coupling and cohesion are that vocabulary.

Microservices are a solution to organizational scaling problems, not a technology choice. Here’s how to tell whether you actually have the problem they solve, before you pay the cost.

You don’t need PostGIS or a geohash library to cache repeat road-distance lookups: rounding coordinates and a unique index gets you most of the win.

Road distance, not straight-line distance, is what travel expense claims and delivery pricing actually need, here’s how to get it without a metered maps API.

Keeping a post and its images together with Hugo page bundles, plus the built-in figure shortcode.

Hugo ships with built-in syntax highlighting via Chroma, no plugins required.

A quick hello and a look at how this site is put together.