Meeting with the legal team — context dump

The hardest part of a 1-person startup isn't the work — it's the lack of a forcing function. Without a meeting on Tuesday, nothing has to ship on Monday. The schedule has to come from somewhere, and "because I said so" isn't enough.

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.

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.

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

swiftCopy
// SwiftUI: keep all five tab views mounted across tab switches so
// each view's @StateObject model persists.
ZStack {
    ForEach(AppTab.allCases, id: \.self) { tab in
        view(for: tab)
            .opacity(router.selectedTab == tab ? 1 : 0)
            .allowsHitTesting(router.selectedTab == tab)
    }
}

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.

sequenceDiagram
  participant U as User
  participant M as Memory.Wiki
  participant A as AI
  U->>M: Save thought / URL / photo
  M-->>U: Permalink
  U->>A: "Use [URL] as my context"
  A-->>U: Answer grounded in the hub

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.