Notes on naming things
The two hard problems in software, minus the joke. Why a good name is a design decision.
A good name is a tiny act of design. It sets an expectation, draws a boundary, and tells you what belongs inside and what does not. A bad name quietly corrupts everything downstream of it.
Spend the extra ten minutes. The name will outlive the code.
