# A Quiet Agreement

## What the name suggests

coding-guidelines.md sounds like a note left on a shared desk. Not a law book, and not a performance. Just a page meant for the next person who has to continue the work. The name is modest on purpose: coding, then guidelines, then a plain ending that asks to be read rather than admired.

## Markers, not walls

Useful guidelines do not try to own every choice. They mark the places where people often get lost: how we name things, how we leave a function, how we say what changed. A marker on a path does not walk for you. It only says that this way has been walked, and that it held.

Writing them down is a small act of care. We would rather agree in daylight than argue late, when everyone is tired and the review has become a contest of taste. The page keeps the shared parts steady so the interesting parts can stay free.

A guideline earns its place when it can answer three plain questions:

- What should we do?
- Why does it matter?
- When may we bend it?

## The kindness of being clear

Picture someone new opening the file on a Sunday evening in mid-October, the light already gone, hoping the words will not show off. If the sentences are calm, they can begin Monday without performing. That is the meaning I take from the name. Guidelines are a form of hospitality. They make the common path obvious, and they trust people with the rest.

*A guideline is a hand on the shoulder, not a hand on the wheel.*