> For the complete documentation index, see [llms.txt](https://training.callysto.ca/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://training.callysto.ca/philosophy/tools1.md).

# Software tools - Eat Your Own Dogfood

"Eat your own dogfood" means that, as developers, we should be using the same tools we are developing for our clients. (The slogan originates with Microsoft.)

For the Callysto project, the tools we want Callysto creators and developers to use are:

* Jupyter notebooks, accessed on the [hub](https://hub.callysto.ca/).
* Python, Markdown, and HTML/Javascript programming languages for coding.

The advantages of using our our own tools are manifold:

* Content will work as expected across platforms.
* Machine independent performance.
* Universal development environment.
* Single platform to maintain.

However, some of the disadvantages of this approach include:

* Constant internet access is required.
* Server hosting the [hub](https://hub.callysto.ca/) needs to be constantly available.
* Packages you have locally will need to be installed on the [hub](https://hub.callysto.ca/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://training.callysto.ca/philosophy/tools1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.