# A Note Left for the Next Pair of Hands

## What the name is really saying

coding-guidelines.md sounds less like a rulebook and more like a file someone meant to leave open. The words are ordinary on purpose. Coding is the work. Guidelines are the shared habits around that work. The ending, md, hints that the advice should live as plain writing, something a person can open and read without a special key.

A guideline is not the program. It is the small agreement that keeps the program from becoming a private language. It answers questions before they turn into arguments: what we call things, how far a change should reach, when to stop and ask.

## Markers, not walls

Think of a path through familiar woods. A wall says stay out. A marker says others have walked here, and this way stays clear in low light. Good guidelines work like markers. They do not replace judgment. They save judgment for the moments that actually need it, so no one spends the morning inventing the same small decisions alone.

That is a quiet kind of care. The person who writes the note may not be in the room when it is needed. The note still sits there, patient, on an ordinary day such as 19 October 2026, ready for whoever arrives tired or new.

A few habits keep the markers honest:

- Say why a habit exists, not only what it asks.
- Prefer the choice a tired person can still follow.
- Change the note when the work changes, and say that you did.

## Room to breathe

Strict pages can make people careful in the wrong way. They copy the letter and miss the point. A thoughtful guideline leaves a little air. It names the usual path, then trusts the reader to step aside when the ground is different. Trust, written down, is still trust.

When the note is short and kind, the work feels less like a test and more like a kitchen left ready: tools in reach, a light on, no mess waiting as a surprise.

*A guideline is a kindness you write down so it can outlast your memory.*