---
mw_bundle: 1
id: f85488fadc01
title: "Pinned for the team"
url: https://memory.wiki/b/f85488fadc01
document_count: 3
updated: 2026-05-11T06:05:00.000Z
source: "Memory.Wiki"
---
# Pinned for the team

> Pinned for the team — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.

**Intent:** decompose

## Documents

### 1. [Letter to a future hire](https://memory.wiki/e6c954035423)
The interesting thing about long-context models isn't that they can read more — it's that they finally make the *retrieval* problem optional. When a model can hold the whole repo in context, the question shifts from "what should I fetch?" to "what should I show?". That's a UX question, not an infrastructure one.

### 2. [Skeleton placeholders are an underrated upgrade](https://memory.wiki/59d449cb1db1)
A good error message answers three questions: what happened, why it happened, and what to try next. Most ship the first, hint at the second, and forget the third. The fix is usually a single sentence longer.

### 3. [Why long-context models change the retrieval calculus](https://memory.wiki/5e4777a425dc)
Long-context AI models shift the retrieval landscape because user context can now be exported as portable, public URLs that function as infrastructure independent of any single AI vendor, making the permalink rather than the API key the critical primitive.


_Digest view — follow any link above to fetch that doc's full markdown. Add `?full=1` to this URL for the concatenated payload._