---
title: "JSON schema for a doc with attachments"
url: https://memory.wiki/e7a714048331
updated: 2026-03-23T07:23:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
concept_count: 7
source: "Memory.Wiki"
---
# JSON schema for a doc with attachments

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.

Reading other people's code is a higher-leverage activity than writing your own. You learn three things at once: what works, what doesn't, and why someone smart picked the trade-off you'd never have considered. The ratio of read-to-write hours quietly separates the engineers who plateau from the ones who keep compounding.

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.

```bash
# Resize + WebP-encode every PNG in the current folder.
for f in *.png; do
  sips -Z 1280 "$f" --setProperty format webp --out "${f%.png}.webp"
done
```

## Next steps

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.

---

## Concepts in this document
- **Markdown** _(concept)_
  A format that succeeded due to low switching costs despite not being the best in any single category.
- **Error message design** _(concept)_
  Example of product quality where most implementations skip the third critical element: actionable next steps.
- **Switching cost** _(concept)_
  The barrier preventing users from adopting alternatives, identified as Markdown's primary competitive advantage.
- **Good enough principle** _(concept)_
  Products win by meeting user needs adequately across domains rather than optimizing for single dimensions.
- **Code reading practice** _(concept)_
  Reading code is higher-leverage than writing because it exposes trade-offs and compounds engineer skill over time.
- **Engineering skill compounding** _(concept)_
  Differential growth factor between engineers who plateau versus those who continuously improve through learning.
- **Image encoding** _(tag)_
  Bash script for batch converting PNG images to WebP format with resizing.

## Concept relations (within this doc's concepts)
- **Code reading practice** drives **Engineering skill compounding**
- **Error message design** instance of **Good enough principle**
- **Markdown** demonstrates power of **Switching cost**
- **Markdown** exemplifies **Good enough principle**
- **Markdown** wins through low **Switching cost**
- **Good enough principle** creates **Switching cost**
- **Markdown** dominates through **Switching cost**
- **Markdown** leverages **Switching cost**

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