r/dataengineering
I spent the last year working in Palantir Foundry... and now I'm back to Snowflake
- upvotes
- 17
- comments
- 21
Post
Highlighted: the lines this signal was extracted from
Palantir Foundry... two words that just might get you crucified around here. At least... they seem to bring out the worst in people on this sub and I kind of see why and also kind of don't.I spent the last 11 months or so working in Foundry and just recently made the jump back into the Snowflake ecosystem... which, for the record, I'm very happy about. That said, I think people around here often misunderstand what Foundry is and is trying to do. Yes, it's a platform or ecosystem and yes there are a lot of "gotchas" and weird/odd things about the platform but it's not truly a DE tool. It's a full-stack tool... that's abstracted. Yes, there are DE related features (python data pipelines, code repositories, git integration) but at its core Foundry is about letting the business make decisions based on ingested data and then write back those decisions to a dataset of some sort.Honestly, it's a unique platform. There's nothing out there, to my knowledge, that does exactly what it does (and yes, its costs and arm and a leg too but... again... nothing does quite what it does). Why did I go back to Snowflake you ask? Well... most of my career (thus far) has been spent in some aspect of data warehousing or data modeling so Snowflake feels like home to me.I think if I had spent more time writing python or working in the full-stack realm Foundry might feel more familiar to me (or...
Keep reading with a free account
The rest of this post, and every signal for Palantir, is in your free account.