02 / Writing
Notes from the build: ambiguity, internal tools, search systems, and the decisions code does not document.
FIELD
NOTES
All dispatches / 4
Written when an implementation detail turns into a reusable idea.
- 01Ambiguity is a signal your ingest pipeline should surface, not swallow.Real corpora don't follow their own conventions. The pipelines that survive that are the ones that treat every naming drift as a first-class output.
- 02Two auth systems, one webapp.The moment your web app has both human users and machine callbacks, one auth strategy stops fitting. Trying to force the fit is where I burned a week.
- 03The two searches you keep confusing.Keyword search and semantic search look like variations of the same idea. They're not. Learning to fuse them — and to trust neither on its own — changed how I think about retrieval.
- 04Quiet software is a design decision.The best internal tools are the ones you stop noticing. That takes more work, not less.