# A Quiet Agreement

## What the name suggests

coding-guidelines.md reads like a note left on a shared desk. Coding is the work of making something that can run. Guidelines are the small agreements that keep that work kind to the next person. The ending, md, is modest: plain words, easy to open, easy to revise. Put together, the name points to a simple idea. Care can be written down, and writing it down is part of the craft.

## Edges, not walls

A useful guideline is closer to a garden edge than to a locked gate. It marks where the path is, so people do not have to guess with every step. It does not need to sound impressive. It only needs to be clear enough that a tired reader can follow it.

Shared notes turn a pile of files into a place. Someone new can enter without feeling shut out. An old mistake does not have to be paid for twice. The point is not control. The point is fewer surprises, and more room to think about the actual problem.

A few habits carry most of the weight:

- Say the ordinary case first, then the exception.
- Prefer one clear way when many clever ways would do.
- Change the note when the work teaches you something better.

## What we hand forward

On 20 October 2026, a file like this is still only words. Its value appears later, when someone opens it beside unfinished work and finds the next step already named. Guidelines grow old. The habit of leaving them does not have to. Each small revision is a way of saying: you were expected here, and you do not have to start from nothing.

*A guideline is a kindness written before it is needed.*