Infrastructure
Your coding agent keeps a diary
Every opencode session leaves a trail in a local SQLite file. dlt turns it into analytics you actually read.
Posts related to hyperscalers (AWS, Azure, GCP) and pipelines (ELT/rETL, streaming, orchestration)
Infrastructure
Every opencode session leaves a trail in a local SQLite file. dlt turns it into analytics you actually read.
Infrastructure
Exit code 137 is dlt's way of saying "your RAM and I need to talk"
Lakehouse
MotherDuck shipped agent-native Python pipelines. The obvious thing to run inside one is dlt.
Infrastructure
Bring your own model, ditch the subscription.
Infrastructure
Why let a search engine guess what context your model needs? Perplexity's new Search as Code hands the reins to the agent.
Infrastructure
Moved a dlt pipeline off SPCS onto dltHub Pro. Still want Snowflake to push the button.
Infrastructure
How I kept IP‑locked Snowflake and Azure databases happy with a managed runtime that runs “wherever Python runs”
Infrastructure
Three vendors, one week, one direction: the cloud-only assumption for AI agents is cracking.
Snowflake
A single boolean on AI_COMPLETE, a Llama Guard 3 wrapper, and a hardcoded filter string. Useful, cheap, and nowhere near enough on its own.
Lakehouse
Cortex Code stopped being “just another AI feature” the moment skills landed. In under three months they’ve become the missing glue: portable, versioned building blocks that turn NPO data stacks into repeatable agent workflows.
Infrastructure
Anthropic is scrambling for GPUs, AMD is finally shipping drop‑in AI cards, and Zyphra just proved you can train real models on a full AMD stack. All of that lands in your Snowflake account the moment you run create compute pool
Lakehouse
Build-vs-buy got rewritten by agentic coding. So I retired the legacy BI tool. 😎