You do use AI!
And I do too, I started my work with AI about 2 years after you did, and the experience and opinions I have match yours to a T. However, I have tried AI to do things from scratch multiple times, and the fact still remains that you have to gently nudge it like you would a junior dev. This is not a new discussion but its still worth mentioning.
About music generation, I feel nervous when AI and art intersect, might be because of my background and art hobbies.
Finally, boring AI is probably the best AI out there. Silently ironing out the issues and friction we face in our day-to-day without really being very flashy and glam. Also worries me that we are calling everything AI lately even if its ML or just a smart algorithm. Good for marketing, I guess.
The key insight about bloom filters lacking synergy is excellent. The ~7K document crossover point makes sense because inverted indexes amortize dictionary storage across all documents while bloom filters must encode it linearly per document
I got tired of re-explaining my codebase to Claude and Copilot every session. They forget everything—architecture, patterns, conventions. It's like talking to a goldfish.
So I built In Memoria: an MCP server that gives AI assistants persistent memory. It learns your coding patterns from your actual code (via tree-sitter) and provides that context to any MCP-compatible AI.
How it's different from RAG or Cursor rules:
- Not just retrieval: It learns patterns statistically ("90% of your functions return Result<T>")
- Not static config: Learns from actual code structure and usage
- Local-first: Rust core for speed, everything stays on your machine
Since launch: 86 stars, 14 forks, and yesterday we got 2 PRs for PHP support from external contributors I've never met. People are building features I haven't had time to implement, which is wild.
Works with Claude Desktop, Claude Code, Copilot, Cursor, anything that supports MCP. Install via `npx in-memoria server`.
What's the most annoying thing your AI assistant forgets? I'm prioritizing the roadmap based on real pain points.