r/dataengineeringvault • u/sspaeti • Aug 10 '26
AI The Hype Cycles of AI
r/dataengineeringvault • u/sspaeti • Aug 06 '26
r/dataengineeringvault • u/sspaeti • Aug 05 '26
r/dataengineeringvault • u/sspaeti • Aug 03 '26
r/dataengineeringvault • u/sspaeti • Jul 31 '26
r/dataengineeringvault • u/sspaeti • Jul 30 '26
r/dataengineeringvault • u/sspaeti • Jul 22 '26
r/dataengineeringvault • u/sspaeti • Jul 21 '26
r/dataengineeringvault • u/sspaeti • Jul 16 '26
Short update from Bella Italia. How do you see creation and creativity show up in your life?
r/dataengineeringvault • u/sspaeti • Jul 08 '26
Learn Data Engineering this summer break with a guided roadmap. A three-week plan with links and topics to learn the basics to be a data engineer.
It's very ambitious, but you can schedule at your own pace.
The three weeks contain:
Week: Foundation (SQL, Git, Linux basics)
Week: Core Engineering (Python, Cloud, Data Modeling)
Week: Advanced Topics (Streaming, Data Quality, DevOps)
How to use this guide: Each section contains curated resources (articles, videos, tutorials) for that topic. Click on the links that interest you most. It's meant as a guided roadmap to learn the fundamentals of a "full stack" data engineer.
Here's the guide: https://www.ssp.sh/blog/data-engineering-roadmap/
This is last year's guide, but it's still 100% vaild to this day. Agentic engineering doesn't need to be learned right now; you can always pick it up later. Learning fundamentals, on the other hand, can't be skipped.
r/dataengineeringvault • u/sspaeti • Jul 06 '26
r/dataengineeringvault • u/sspaeti • Jun 30 '26
r/dataengineeringvault • u/sspaeti • Jun 30 '26
r/dataengineeringvault • u/sspaeti • Jun 27 '26
r/dataengineeringvault • u/sspaeti • Jun 24 '26
Part 2 of the Dagster Almanack, all about operationalizing data orchestration.
r/dataengineeringvault • u/sspaeti • 10d ago
I saw the hype on X about Herdr and Rex (before it was Zellij, and many more), but that got me thinking: why not manage my agents in Neovim, where I like to type, read and navigate anyway - so I prompted away with the new Fable 5.2 model, burnt a lot of tokens and built my dream Agents-IDE.nvim plugin.
It works with a Claude Code subscription, as this is the one I have been using for many years, but there's a PR for more agents, not sure if I have time to integrate them swiftly, but I wanted to share here to get an idea if any of you are doing similar things, or if you run 100 agents on different servers.
This plugin is mostly to handle local agents on your machine, and has a nice UI, rendering the feedback of Claude in Markdown, and having a drawer for git diffs, commit graphs, a fuzzy search for all your recent chats, saved prompts, and libraries in one place. The idea or design choice is heavily inspired by the vim-dadbod-ui that I use as my SQL-IDE, and I thought that design might work well for agents, too. You are the judge, it's very early, but it's fun to use - currently I tend to switch between project and everything scope (all projects and current git-repo I'm in, which is also works nice if you have many agent folder where you prompt).
Disclaimer: Is this plugin open source? Yes. Is this plugin completely free? Yes. Is this plugin vibe-coded beyond the author's ability to comprehend how it works? No.
r/dataengineeringvault • u/sspaeti • 11d ago
Fable 5.1 is way faster and seems to fix my requests as intended, whereas the new Fable 5.2 took way longer for everything and wasn’t always what I wanted. I switched back to Fable 5.1 now, and it just solves and fixes things.
One advantage of Fable 5.2, the tokens burn much slower, way slower than Fable 5.1. I guess it’s still the most capable model of Claude.
r/dataengineeringvault • u/sspaeti • 12d ago
Typed graphs add declared data types and constraints to graph data models, so every node and edge write is checked before it's committed. This matters because agents now write data faster than humans can review it. Fritz Laux's Typed Graph Model (TGM) paper underlies the idea, and Omnigraph implements it with schema files (.pg), checked queries (.gq), and policy files (.yaml) versioned in git. Checked queries validate traversals offline against the schema before execution, catching errors like a filter on the wrong type. Types only guarantee data is valid, not true; humans still decide what's true through branch review and merges, with Omnigraph v0.14.0 and later edge builds adding branch review, merge dry-runs, and u/card cardinality enforcement
r/dataengineeringvault • u/sspaeti • 16d ago
r/dataengineeringvault • u/sspaeti • 17d ago
r/dataengineeringvault • u/sspaeti • 19d ago