Naming

The Name Gets Out

A name coined in a schema column doesn't stay there. It spreads into API fields, docs, dashboards, and eventually the customer's own sentences — and by the time it's wrong, fixing it is a negotiation, not a refactor.

The Words You Inherit

Every system hands you a vocabulary before it hands you a problem. The names you didn't choose draw the boundaries you can see, and a wrong one doesn't confuse you — it quietly removes designs from consideration.

Words Are Infrastructure

Naming gets treated as a documentation concern — a matter of clarity and taste. It behaves like a schema decision: cheap for an afternoon, load-bearing forever, and reviewed like neither.

The Naming Debt

Variable names and function names accrue meaning over time — and when the name no longer fits the thing, the cost is paid by everyone who reads the code next

Naming Things Twice

The hidden cost of naming something one thing in code and another in conversation