dbt and Fivetran will merge.
https://www.getdbt.com/blog/dbt-labs-and-fivetran-sign-definitive-agreement-to-merge
https://www.getdbt.com/blog/dbt-labs-and-fivetran-sign-definitive-agreement-to-merge
dbt Labs
Fivetran and dbt Labs Unite to Set the Standard for Open Data Infrastructure | dbt Labs
Together, Fivetran and dbt are simplifying enterprise data management with a unified foundation that powers analytics and AI at scale.
LangChain raises $125M to build the platform for agent engineering
https://blog.langchain.com/series-b/
https://blog.langchain.com/series-b/
Langchain
LangChain raises $125M to build the platform for agent engineering
We raised $125M at a $1.25B valuation to build the platform for agent engineering.
👍4
An extensive guide on Snowflake query optimization. Also a talk by the authors if you prefer video.
YouTube
The Missing Manual: Everything You Need to Know about Snowflake Optimization | SELECT
ABOUT THE TALK
Learn all about cost and performance optimization in Snowflake. This talk deep dive's into Snowflake’s architecture & billing model, covering key concepts like virtual warehouses, micro-partitioning, the lifecycle of a query and Snowflake’s…
Learn all about cost and performance optimization in Snowflake. This talk deep dive's into Snowflake’s architecture & billing model, covering key concepts like virtual warehouses, micro-partitioning, the lifecycle of a query and Snowflake’s…
Unlocking Entertainment Intelligence with Knowledge Graph | by Netflix Technology Blog | Nov, 2025 | Medium
https://netflixtechblog.medium.com/unlocking-entertainment-intelligence-with-knowledge-graph-da4b22090141
https://netflixtechblog.medium.com/unlocking-entertainment-intelligence-with-knowledge-graph-da4b22090141
Medium
Unlocking Entertainment Intelligence with Knowledge Graph
Author: Himanshu Singh
👍1
Looks like a cool way for having a personal AI assistant, especially if you have an always on desktop machine at home
https://github.com/moltbot/moltbot
https://github.com/moltbot/moltbot
GitHub
GitHub - openclaw/openclaw: Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞
Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞 - openclaw/openclaw
👎2🤔2
🦐 PicoClaw is an ultra-lightweight personal AI Assistant inspired by nanobot, refactored from the ground up in Go through a self-bootstrapping process, where the AI agent itself drove the entire architectural migration and code optimization.
⚡️ Runs on $10 hardware with <10MB RAM: That's 99% less memory than OpenClaw and 98% cheaper than a Mac mini!
https://github.com/sipeed/picoclaw
⚡️ Runs on $10 hardware with <10MB RAM: That's 99% less memory than OpenClaw and 98% cheaper than a Mac mini!
https://github.com/sipeed/picoclaw
GitHub
GitHub - sipeed/picoclaw: Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity
Tiny, Fast, and Deployable anywhere — automate the mundane, unleash your creativity - sipeed/picoclaw
👍1
ClickHouse MergeTree and HBase are the same thing at their core.
Not literally — but architecturally, they share the same DNA: the LSM Tree (Log-Structured Merge Tree).
Here's how it works:
1. Writes hit memory first → fast, no disk I/O
2. When memory fills, flush to an immutable sorted file on disk
3. Background compaction merges files → removes duplicates, applies deletes
4. Bloom filters + sparse indexes make reads fast without scanning everything
HBase calls these HFiles. ClickHouse calls them Parts. Cassandra calls them SSTables. Same idea.
What ClickHouse adds on top:
★ Columnar layout inside each part (OLAP-optimized)
★ The merge step does useful analytical work — deduplication (ReplacingMergeTree), summation (SummingMergeTree), pre-aggregation (AggregatingMergeTree)
★ Sparse indexing at granule level (8192 rows) rather than row-level
I still teach HBase in my data engineering course — as a NoSQL example and as a core part of the Hadoop ecosystem. And honestly, I started my DE career working with it.
Sometimes I wondered: is this too specific? Should I simplify the curriculum and drop it?
But my teaching philosophy has always been to explain technologies by focusing on what's fundamental and shared across many systems. And this connection — HBase and ClickHouse both rooted in LSM Trees — is exactly why that approach pays off.
The tools change. The patterns underneath them don't.
Not literally — but architecturally, they share the same DNA: the LSM Tree (Log-Structured Merge Tree).
Here's how it works:
1. Writes hit memory first → fast, no disk I/O
2. When memory fills, flush to an immutable sorted file on disk
3. Background compaction merges files → removes duplicates, applies deletes
4. Bloom filters + sparse indexes make reads fast without scanning everything
HBase calls these HFiles. ClickHouse calls them Parts. Cassandra calls them SSTables. Same idea.
What ClickHouse adds on top:
★ Columnar layout inside each part (OLAP-optimized)
★ The merge step does useful analytical work — deduplication (ReplacingMergeTree), summation (SummingMergeTree), pre-aggregation (AggregatingMergeTree)
★ Sparse indexing at granule level (8192 rows) rather than row-level
I still teach HBase in my data engineering course — as a NoSQL example and as a core part of the Hadoop ecosystem. And honestly, I started my DE career working with it.
Sometimes I wondered: is this too specific? Should I simplify the curriculum and drop it?
But my teaching philosophy has always been to explain technologies by focusing on what's fundamental and shared across many systems. And this connection — HBase and ClickHouse both rooted in LSM Trees — is exactly why that approach pays off.
The tools change. The patterns underneath them don't.
👍2
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:
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
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
Ollama
Ollama is now powered by MLX on Apple Silicon in preview· Ollama Blog
Today, we're previewing the fastest way to run Ollama on Apple silicon, powered by MLX, Apple's machine learning framework.
👍4
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.
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
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
GitHub
GitHub - coleam00/claude-memory-compiler: Give Claude Code a memory that evolves with your codebase. Hooks automatically capture…
Give Claude Code a memory that evolves with your codebase. Hooks automatically capture sessions, the Claude Agent SDK extracts key decisions and lessons, and an LLM compiler organizes everything in...
👍1
A drop-in Apache Spark replacement written in Rust, unifying batch processing, stream processing, and compute-intensive Al workloads.
https://github.com/lakehq/sail
https://github.com/lakehq/sail
GitHub
GitHub - lakehq/sail: Drop-in Apache Spark replacement written in Rust, unifying batch processing, stream processing, and compute…
Drop-in Apache Spark replacement written in Rust, unifying batch processing, stream processing, and compute-intensive AI workloads. - lakehq/sail
👍1