← Blog
Week of

Retrospective reconstruction · Published · Weekly archive

Leave enough information to resume

Longer assignments need checkpoints that describe actual state.

Field NotesRetrospective

Retrospective reconstruction of the week beginning 2025-05-26, written on 16 November 2026. This is not a claim of publication at the time.

Google presented Gemini 2.5 updates at I/O on 20 May. Anthropic introduced Claude 4 on 22 May. Longer assignments were becoming a more prominent part of the pitch.

Long work gets interrupted. A connection drops, a tool fails or the person changes direction. “Mostly finished” is a poor place to resume from.

For code, leave the diff, the commands run and the failures still present. For research, leave the decisive sources and the unanswered question. For an external action, record whether it was prepared, submitted or confirmed. That last distinction can prevent a duplicate message or record.

Keep the previous working state where practical. Save intermediate outputs somewhere inspectable. Do not rely on someone scrolling through a long conversation to discover which attempt was the good one.

A checkpoint should be short enough to read and specific enough to act on. If another capable person could continue without asking what happened, it probably contains the right details.

The extra context is worth writing while the task is going well. After an interruption, reconstructing it is slower and much more vulnerable to optimistic guesses.

Sources available at the time

Gemini 2.5 at I/O; Claude 4

All posts Work with me