The bitter lesson in 26 words:
Donβt be distracted by human knowledge, as AI has been historically.
Instead focus on methods for creating knowledge that scale with computation, like search and learning.
We are engineering in the absence of theory and calling it progress. It might be. The question is whether you know which of your problems can be solved with more effort and which ones can't.
seems obvious but:
things that are changing rapidly:
1. context windows
2. intelligence / ability to reason within context
3. performance on any given benchmark
4. cost per token
things that are not changing much:
1. humans
2. human behavior, preferences, affinities
3. tools, integrations, infrastructure
4. single core cpu performance
therefore,
ngmi:
1. "i found this method to cut 15% context"
2. "our method improves retrieval performance 10% by using hybrid search"
3. "our finetuned model is cheaper than opus at this benchmark"
4. "our harness does this better because we invented this multi agent system"
5. "we're building a memory system"
6. "context graphs"
7. "we trained an in house specialized rl model to improve task performance in X benchmark at Y% cost reduction"
wagmi:
1. product/ui
3. customer acquisition
4. integrations
5. fast linting, ci, skills, feedback for agents
6. background agent infra to parallelize more work
7. speed up your agent verification loops
8. training your users, connecting to their systems and working with their data, meeting them where they are
the missing piece is consolidation. humans promote episodic memories to semantic through repetition and emotional salience. current memory systems skip that step entirely and they store everything as equally permanent facts. i think the hard problem is both "what to forget," and more importantly "what to promote"