> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/conference26/session-a-workshops/flare-seeing-the-structure-in-code.md).

# FLARE: Seeing the Structure in Code

How can we help learners understand code rather than simply write it?

This practical workshop introduces FLARE, a developing framework for code comprehension, built around four simple connections: how data and control enter and leave any piece of code. 

You’ll try it on examples ranging from single statements to whole programs, and see how changing the part of the program you focus on reveals connections that are easy to miss. 

You’ll leave with a practical structure for questioning, prediction and discussion in computing science lessons.

{% hint style="warning" %}
Please note

* This session will run twice in anticipation of this being a popular topic, relevant to primary and secondary settings. Choose whichever is convenient to you.
  {% endhint %}

{% hint style="info" icon="school" %}
**Justin Heath**

Classroom Teacher

Arunside School (Primary)
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://upskilling.stacs.scot/conference26/session-a-workshops/flare-seeing-the-structure-in-code.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.