---
title: "Reading log: October-November"
url: https://memory.wiki/53bac621b960
updated: 2026-04-19T03:52:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
bundle_count: 3
concept_count: 5
source: "Memory.Wiki"
---
# Reading log: October-November

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.

Markdown won because it was always good enough. Not the best at any one thing — never the fastest editor, never the prettiest output, never the most semantically rich. But always close enough that the switching cost killed every alternative.

Most personal-knowledge tools optimise for input. The friction is on the way in: capture this thought, file it, tag it, link it. But the value lives on the way OUT — when the system surfaces the right note at the right moment without you asking. Capture-heavy products are easier to build; output-heavy ones are what people actually pay for.

### Capture-flow check-list

- [x] Pulled from Safari via Share Sheet
- [x] OCR'd a whiteboard photo
- [x] Dictated three voice memos walking to coffee
- [ ] Imported the long PDF I was avoiding
- [ ] Cleaned the inbox folder

```python
# Tiny script that prints any URL's title.
import requests, re
def title(url: str) -> str:
    html = requests.get(url, timeout=5).text
    m = re.search(r"<title>(.*?)</title>", html, re.S | re.I)
    return m.group(1).strip() if m else url
print(title("https://memory.wiki"))
```

> "Make the easy thing the default and the hard thing possible."
> — design rule I keep stealing from Linear

```mermaid
flowchart LR
  Capture --> Organize
  Organize --> Use
  Use -.indispensability loop.-> Capture
```

![Whiteboard sketch](https://images.unsplash.com/photo-1551288049-bebda4e38f71?w=1200&q=80)

## Next steps

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.

---

## Concepts in this document
- **Output-Heavy Systems** _(concept)_
  Knowledge tools that prioritize surfacing information over capturing it.
- **Linear** _(entity)_
  Design philosophy benchmark for default-easy, hard-possible workflows.
- **Long-Context UX** _(concept)_
  The shift from retrieval-based systems to presentation-based systems.
- **Permalink Infrastructure** _(concept)_
  Using public URLs as a vendor-agnostic portability layer.
- **Forcing Functions** _(concept)_
  External constraints required to maintain productivity in solo ventures.

## Concept relations (within this doc's concepts)
- **Long-Context UX** enables better **Output-Heavy Systems**

## Bundles containing this document
- [Personal-knowledge-management notes](https://memory.wiki/b/400b3906b96a)
  > Personal-knowledge-management notes — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.
- [v8 launch plan](https://memory.wiki/b/ce89afb82fe7)
  > v8 launch plan — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.
- [App Store submission checklist](https://memory.wiki/b/bf24c8b646ef)
  > App Store submission checklist — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.

_Hub canonical:_ https://memory.wiki/hub/memorywiki-demo
_Concept digest:_ https://memory.wiki/raw/hub/memorywiki-demo?digest=1&compact=1