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

flowchart LR
  Capture --> Organize
  Organize --> Use
  Use -.indispensability loop.-> Capture
Whiteboard sketch
Whiteboard sketch

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.