# How to read code better

### Objectives :

* Understand how our brain works in front of code
* Get some tips to improve our daily life
  * Flashcards to learn quickly new syntax / spaced repetition
  * Chunking code strategies
  * Techniques to read complex code

## Connection - Code reader 10'

![](/files/-MiegjCnc_ZOIW6jxbLp)

Ask participants to :

* Choose a code snippet
* Take a few minutes to read / understand it - 5'
* Add notes on your snippet - 5' 
  * Why did you choose this piece of code ?
  * What makes it easy to understand the code ?
  * What makes it hard to understand the code ?

{% file src="/files/-Miegrl65D3iU\_7WaQzc" %}
Code snippets examples
{% endfile %}

Debrief it and relate to the confusion related to code.

## Concepts - 30'

{% embed url="<https://speakerdeck.com/thirion/the-programmers-brain-read-code-better>" %}

## Concrete Practice -  Create your own Flashcards 10'

* Think of the top 10 programming concepts you always have trouble remembering
* Make a set of flashcards for each of the concepts and try using them

**Example** :

![](/files/-Miejuuvw1Ei-5XEM4Rk)

## Conclusion - 5'

* Debrief on the learning of the day
* Ask participants to stick their name
* Ask them why here

![](/files/-Miek50oP5ZHWIs-RqUR)


---

# 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://yoan-thirion.gitbook.io/knowledge-base/software-craftsmanship/the-programmers-brain/how-to-read-code-better.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.