> For the complete documentation index, see [llms.txt](https://grofit.gitbook.io/halp-i-want-to-learn-how-to-code/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://grofit.gitbook.io/halp-i-want-to-learn-how-to-code/thinking.md).

# Thinking about stuff

This section is less about **DOING** and more about learning about the basics of code and the commonality most programming languages share.

You wont be needing do anything practical here, just read over and attempt to understand whats going on.

For the most part code examples will be succinct and will be explained, there will be a few examples showing different languages side by side, which may seem scary at first, but as we are not trying to teach **one language** but teach the **fundamentals of programming** it should actually make things easier in the long run.

Once we have discussed at a high(ish) level the basic bits of code we can then dive into writing some code and seeing what happens.


---

# 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://grofit.gitbook.io/halp-i-want-to-learn-how-to-code/thinking.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.
