# Coding Guidelines

## The Quiet Shape of Care

A codebase is not a collection of instructions. It is a letter written to the people who will read it long after we have moved on. Every name we choose, every blank line we leave, every decision to keep something simple instead of clever becomes part of that letter. The domain name itself, coding-guidelines.md, reminds us that these rules are not laws carved in stone. They are gentle agreements between people who care about the same thing.

When we write code, we are also writing a promise: that the next person will not have to struggle in the dark. Good guidelines turn that promise into habit. They ask us to slow down just enough to consider the reader who will arrive at three in the morning, tired and under pressure. In that moment our earlier restraint becomes an act of kindness.

## Small Choices, Long Echoes

The best guidelines rarely feel dramatic. They live in the small decisions: using the same word for the same concept, keeping functions short enough to fit in one glance, writing comments that explain why instead of what. These choices accumulate like stones in a riverbed. Over time they guide the flow of work so naturally that people stop noticing the guidance at all. They simply feel that the code is calm.

We do not need many rules. We need clear ones that we actually follow. A short list respected by everyone matters more than a long list ignored by most.

- Choose clarity over cleverness
- Prefer obvious over impressive
- Fix the small confusions before they grow

## The Real Purpose

Guidelines are not about perfection. They are about respect. Respect for future teammates, for our own future selves, and for the quiet work of keeping software understandable year after year.

*On October 5, 2026, we remember that good code begins with thoughtful restraint.*