URL → markdown conversion (server-side recipe)

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.

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.

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.

bashCopy
# 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

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

The model's loss on the held-out set converged to $\mathcal{L} = 2.41$ after roughly $1.2 \times 10^4$ steps — well above the chance baseline of $\log_2 50{,}000 \approx 15.6$ bits per token but still leaving room for the next architecture pass.

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

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

Recap

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.