---
title: "Travel notes: Seoul → Tokyo"
url: https://memory.wiki/cd48bf42bf7c
updated: 2026-03-13T10:56:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
bundle_count: 1
concept_count: 8
source: "Memory.Wiki"
---
# Travel notes: Seoul → Tokyo

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.

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.

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.

### Today's reading list

1. *Designing Data-Intensive Applications* — chapter 5 (replication)
2. The Hacker News thread on "What I learned writing a JIT"
3. A Stripe engineering blog post about idempotency keys
4. Karpathy's tweet thread about LLM evals

```typescript
// Server-sent events from /api/import/url
const res = await fetch("/api/import/url", {
  method: "POST",
  headers: { "Content-Type": "application/json", Accept: "text/event-stream" },
  body: JSON.stringify({ url })
});
for await (const chunk of res.body!) {
  // parse SSE: 'event: stage' / 'data: {...}'
}
```

| Provider | Strength | Weakness |
|---|---|---|
| Claude | Long context, instruction following | Slow for tiny prompts |
| GPT-4o | Multimodal, fast | Drifts on long sessions |
| Cursor | Code-aware ranking | Locked to editor |

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

![Calm reading nook](https://images.unsplash.com/photo-1507842217343-583bb7270b66?w=1200&q=80)

The thesis here[^1] is that delivery model matters more than retrieval quality.

[^1]: First articulated in the W6 internal note "Graph RAG is delivery, not retrieval."

## Recap

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.

---

## Concepts in this document
- **Markdown** _(concept)_
  A format that succeeded due to low switching costs despite not being the best in any single category.
- **GPT-4o** _(entity)_
  Multimodal AI provider referenced in comparisons.
- **Claude** _(entity)_
  AI provider cited for long-context capabilities.
- **Delivery model** _(concept)_
  Focus on how information is delivered to the user; argued as more important than retrieval quality.
- **Error messages** _(concept)_
  A design pattern requiring clear explanation of what, why, and what next.
- **Server-sent events** _(concept)_
  Streaming update mechanism used in examples.
- **Switching costs** _(concept)_
  Economic friction that protects incumbent solutions from being displaced by technically superior alternatives.
- **Idempotency** _(concept)_
  Technical pattern referenced in reading list as relevant to system reliability design.

## Concept relations (within this doc's concepts)
- **Markdown** succeeds through **Switching costs**
- **Error messages** exemplifies importance of **Delivery model**
- **Server-sent events** implements streaming pattern for **Delivery model**
- **GPT-4o** compared against **Claude**
- **Claude** compared with **GPT-4o**

## Bundles containing this document
- [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.

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