> For the complete documentation index, see [llms.txt](https://sp.jerrygems.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sp.jerrygems.tech/volume-iv-the-indicative-engine-and-verb-conjugation/27-preterite-vs-imperfect-the-epic-duel.md).

# 27. The Epic Duel: Preterite vs. Imperfect

> *The definitive guide to conquering the past: completed events vs. ongoing stage background.*

***

## The Heart of Spanish Storytelling

English speakers constantly struggle with the past because English uses one simple past tense (*"I ate", "I ran"*). Spanish forces you to choose based on **aspect**:

### The Golden Analogy: The Movie Scene

* **The Imperfect is the Camera Background Setting:**
  * Weather: *«Hacía mucho frío.»* (It was very cold.)
  * Time: *«Eran las diez de la noche.»* (It was 10:00 PM.)
  * Age & Physical State: *«Yo tenía diez años y estaba cansado.»* (I was 10 and was tired.)
  * Ongoing habits: *«Siempre comíamos juntos.»* (We always used to eat together.)
* **The Preterite is the Sudden Actor Bursting onto Stage:**
  * Sudden action: *«De repente sonó el teléfono.»* (Suddenly, the phone rang!)
  * Completed event: *«Ayer compré una bicicleta nueva.»* (Yesterday I bought a new bicycle.)
  * Fixed duration: *«Viví en Madrid durante dos años.»* (I lived in Madrid for 2 years — finished!).

***

### Daily Life Multi-Level Practice

* 🟢 **Level 1:** *«Ayer cené con mis amigos y luego fuimos al cine.»* (Yesterday I had dinner with my friends and then we went to the cinema.)
* 🟡 **Level 2:** *«Mientras yo leía un libro en la sala, se fue la luz por completo.»* (While I was reading a book in the living room, the power went out completely.)
* 🔴 **Level 3:** *«Durante décadas el pueblo creía en la leyenda, hasta que en 1985 unos arqueólogos descubrieron la verdad.»* (For decades the town believed in the legend, until in 1985 archaeologists uncovered the truth.)


---

# 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://sp.jerrygems.tech/volume-iv-the-indicative-engine-and-verb-conjugation/27-preterite-vs-imperfect-the-epic-duel.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.
