Skip to main content
computer-science languages-and-literature

​
In medias res

​
Description

Entry into a process at the middle, not the beginning — the audience or consumer is dropped into action already underway; backfill, origin, or setup arrives later (through flashback, progressive exposition, or “you’ll figure it out as you go”). The concept’s structural shape is mid-cycle entry + delayed backfill + the entry-point is rhetorically chosen, not chronologically natural. The diagnostic distinguishes deliberate-mid-entry (in-medias-res) from missing-context-as-bug (the system genuinely lacks the setup the consumer needs). In-medias-res is a choice — the author/designer has decided that starting in the middle is more effective than starting at the beginning. The concept recurs because hooking attention often beats establishing context; the cost is consumer disorientation that must be paid back later.

​
Triggers

User-initiated: User asks about entry-points, “where should we start the user?”, or describes drop-in vs setup-first design. Vocabulary cues: “in medias res,” “drop in,” “cold open,” “lead with,” “TL;DR,” “start with the action.” Agent-initiated: Agent notices a system or narrative deliberately starts after natural beginnings, with backfill following. Candidate inference: “the in-medias-res move is making this consumable; is the deferred backfill being delivered well enough?” Situation-shape signals: API endpoints accepting ID-references to existing state. Documentation organized by tasks rather than concepts. Conference talks that lead with the punchline. Tutorials that don’t require completing the previous chapter first.

​
Exclusions

  • Chronological-required narratives — formal proofs, step-by-step recipes that genuinely require ordering; in-medias-res forces a frame the content can’t support.
  • Cold-start with no recovery path — if the consumer enters at the middle but never gets the backfill, the concept fails — it’s not in-medias-res, it’s broken-onboarding.
  • Trivially-short content — a one-paragraph email doesn’t have “middle” or “beginning” in a meaningful sense.
  • Educational settings where prerequisites are load-bearing — sometimes you genuinely need the foundation before the application; in-medias-res in math instruction can lead to memorizing-without-understanding.

​
Structure

Internal structure of in-medias-res: a table of its component slots and the concepts that fill them.

​
Relationships

Relationship neighborhood of in-medias-res: a graph of the concepts it connects to and the concepts it is a part of.
  • cadence — in-medias-res is a cadence move; rhetorical timing of entry chosen for effect.
  • seeding — contrast: seeding emphasizes the initial-input shape-determination; in-medias-res deliberately starts past the seed.
  • bookends — contrast: bookends frame from outside-natural-temporality; in-medias-res enters inside-natural-temporality without the explicit opening.
  • multi-hop-routing — in-medias-res often pairs with multi-hop-routing in narrative — entering at hop N rather than hop 0; per-hop local context becomes the consumer’s foothold.
  • surface — the entry-point surface is what matters; the back-content can be deferred behind that surface.

​
Examples

TV pilots: cold opens · languages-and-literature

drop the viewer into action before titles; backfill character introductions in subsequent scenes.

Onboarding into running systems · computer-science

new hires join mid-incident or mid-project; backfill comes from documentation + colleague conversations.
Aristotle’s Poetics discusses where dramatic plots should begin and end, treating the question of starting-point as a design decision rather than a fact of the underlying events. The argument anticipates the in-medias-res principle without naming it: the chronological beginning of a story’s events is not necessarily its rhetorical beginning.The treatment is implicit rather than prescriptive — the Poetics is more focused on unity of action than on opening conventions — but the move it makes is the same one Horace later formalized: the audience can be inserted into the middle of action, with backfill following, when the middle is the part that earns the audience’s attention.
the user is dropped into “how to” and learns concepts as they appear; modern README discipline.
Horace’s Ars Poetica names the principle as advice for epic poetry: don’t begin from first events; begin from the middle of action (“in medias res”), and let the audience be carried into the narrative by the urgency of what is happening rather than by the chronological scaffolding leading up to it. The Iliad opens in the tenth year of the Trojan War, with Achilles’ wrath rather than the war’s origins; the Odyssey opens after the war is over.The same opening discipline transfers cleanly across very different surfaces. API design exposes endpoints that accept partial state, letting clients pick up the system mid-flow rather than building it up from a fresh initial condition. Documentation often works better when it leads with use-cases rather than with installation and prerequisites — the reader needs to know what the tool does before the setup costs feel justified. Presentations using BLUF / TL;DR put the conclusion first, letting the audience decide how much of the supporting structure they need.Inference: When designing the first thing a reader, user, or client encounters, the question is not “where do the events start?” but “where does attention come alive?” Backfill the prerequisites only as their absence starts to bite.
The Iliad opens not with the abduction of Helen, not with the assembly of the Achaean ships, not with Paris’s judgment — it opens nine years into the Trojan War, mid-quarrel, with Achilles’s wrath at Agamemnon’s seizure of Briseis. “Sing, goddess, of the wrath of Achilles” plants the audience squarely in mid-cycle; the war’s origins, the alliances, the prior battles all arrive later through retrospective reference, embedded songs, and characters’ recollections. Horace’s Ars Poetica later named this technique, prescribing that epic poets in medias res non secus ac notas auditorem rapit — “snatch the audience into the middle of things as if into the already-known.”Inference: Horace’s canonical example is a worked instance of why in-medias-res is the default opening for high-stakes narrative: the audience is engaged before context is required, and the gap between opening and backfill becomes itself a source of pull. The same structural choice operates in technical writing (a tutorial that opens with a working program rather than a chapter of background; a postmortem that opens with the customer-visible failure rather than the system architecture) and in agent design (an agent that responds first to what the user actually said, then surfaces clarifying context, rather than gating the response behind a long preamble). The discipline is that the backfill must arrive — in-medias-res without recovery becomes broken-onboarding, the exclusion the concept guards against.
start with the conclusion; backfill the reasoning.
REST endpoints often work in-medias-res (“update user 123”) without requiring full context.
REST as articulated in Roy Fielding’s 2000 dissertation makes server resources addressable by URL, with state carried in the resource itself rather than in a session built up across calls. The consequence is that a client can enter the system “in the middle” — GET /orders/123 is a coherent request without the client having walked through the order’s creation history. The resource is its own backfill.This is the structural cousin of the narrative convention. The chronological history that produced the current state is real, but the client does not have to traverse it; the addressable representation lets the interaction start mid-process. Stateless protocols generalize this — every request carries enough context to be interpreted on its own, so any moment can be an entry point.Inference: When an API requires a long preamble of setup calls before useful operations are possible, the surface is failing the in-medias-res test. Restructure so that the interesting endpoints accept enough context to be called directly.
backfill comes from progressive revelation, not pre-loaded mental model.
TV Tropes catalogs “In Medias Res” with a large set of cross-genre examples — film cold-opens, TV pilot openings, novel first chapters, video game tutorials that drop the player into an action scene before any character creation. The breadth of the TV Tropes coverage is itself evidence that the principle has settled into a recognizable convention across narrative forms.The page is useful as a corpus check for the catalog: if a structural shape is documented at TV Tropes with dozens of independent instantiations across genres, the cross-domain reach claim is strong.