Data1984
777 subscribers
48 photos
1 video
17 files
783 links
This channel is mostly about data related stuff, some of the main topics are #DataEngineering #AI #SQL #Python #cloud

Contact: @gorros
Download Telegram
I just learned you can run Claude Code locally with Ollama.

Ollama 0.19 (preview, released yesterday) is now powered by Apple's MLX framework β€” and one thing that caught my attention as a Claude Code user: Ollama now reuses its cache across conversations, meaning less memory overhead and more cache hits when using a shared system prompt with tools like Claude Code.

That's a meaningful improvement for agentic workflows.

The setup is a single command:

ollama launch claude --model qwen3.5:35b-a3b-coding-nvfp4

Whether you're working in an air-gapped environment or just tired of API costs β€” local coding agents are getting genuinely viable.

(Requires a Mac with 32GB+ unified memory)

https://ollama.com/blog/mlx
πŸ‘5
Karpathy posted his raw/ folder workflow for LLM context β€” a simple idea: dump your notes, PDFs, papers into one folder and feed it to the LLM.
Someone built a full system on top of it for Claude Code.

claude-memory-compiler hooks into your Claude Code sessions and automatically compiles them into a structured knowledge base. Every decision, pattern, lesson β€” extracted and cross-referenced into markdown articles.

The architecture is interesting:
β€’ No RAG, no vector DB β€” just a smart index.md the LLM navigates
β€’ Works at personal scale (50–500 articles) better than cosine similarity
β€’ Runs on your existing Claude subscription, no extra API costs
https://github.com/coleam00/claude-memory-compiler
❀2πŸ‘1
SLayer - an open-source semantic layer for AI agents.
The usual argument for giving agents more context is that it helps them write better SQL. SLayer takes a different angle: the problem isn't that agents write bad SQL, they're generally fine at that, it's that they don't know which SQL answers the question, so they guess, and the guess looks just as confident as a correct one. Same question, different query, sometimes a different number.
Instead of feeding the agent more context and hoping it reasons its way to the right query, SLayer gives it a governed set of pre-defined metrics to call. The agent still picks what it needs, but it never decides what "revenue" means or which tables to join, so the same question always returns the same, traceable answer.
Built by the team behind Motley, running as a library, CLI, or MCP/REST interface, no separate service required.
GitHub: github.com/MotleyAI/slayer
X: x.com/usemotley
Website: motley.ai/slayer
πŸ‘8πŸ”₯8❀3😁2
Kimball's entire dimensional modeling playbook condensed into short guide.
πŸ‘3
Recently I have implemented warehouse tiering unaware of this product. In my case most models didn't have dependencies. But the interesting part is that clustering doesn't mean you should not consider using multiple clusters.
❀1πŸ‘1
Edelbyte left stealth with $70M (Sequoia, Quiet Capital) at a ~$500M valuation. The four founders are ex-Azure Kusto (Azure Data Explorer) people, building agent-oriented search and analytics for hundreds of petabytes. It will compete with Snowflake, Databricks and ClickHouse. https://siliconangle.com/?p=853911
❀1