# A Note on Documentation

Along the development cycle, we will learn many new things, formulate many new ideas, make many mistakes, and make many new memories. These memories are meaningful so we should make an effort to preserve them to aid in future developments. This is why we encourage good documentation.

{% embed url="<https://www.youtube.com/watch?v=tJ-LivK4-78>" %}

## What Is "Good" Documentation?

This is a purely subjective statement, but one which we should not have much trouble understanding. A good documentation is simply one which makes an effort to be understood. As the human language is complex and multi-faceted, there is no perfect formula for understanding, all that we are asking is that we try to explain ourselves as best we can, as often as possible.&#x20;

## Why Good Documentation Matters:

1. It helps us keep track of what we have done.
   * This helps us remember what we did.&#x20;
2. It gives us a reference point when we want to make something new.&#x20;
   * This way we do not attempt to re-invent the wheel.
3. It helps us formulate logical abstractions.
   * Thorough understanding makes it easier to develop higher-level concepts based on what we have already done.&#x20;

When we take time to reflect on what we have done, we have a chance to experience it from another perspective. It is easy to get caught up in the stress of the moment -- Deadlines, delays, deliverables are all realities that we must deal with.  Providing ourselves information that makes it easier to deal with these realities as they unfold is only a benefit to us in the long run.&#x20;

## Good documentation is hard

It is the culmination of countless hours of attempted understanding and so it only comes with hard work and excruciating attention to detail. That being said, we have one simple request...

Please, to the best of your abilities, document your work. In the end we will all be thankful.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rairprotocol.org/rairprotocol/codebase/a-note-on-documentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
