Palantir init

I have just read through the initial documentation Indroduction to Foundry & AIP for Enterprise Organizations. The Ontology looks similar to the Ubiquitus Language from Eric Evans Domain Driven Design. It makes sense. The challenge for outside organizations is they cannot define the business process that currently work. An outside products success relies on knowledge from the business.

The products I am most interested in learning about next are Foundry and Apollo. Foundry appears to be the data ingestion system, while Apollo looks like it encompasses the whole SDLC. I may have to ditch git, GitHub and kubernetes.

Palantir Developers 2026

This is a talk from DevCon 2026. I notice it the foundry cli has a template for a project that looks much easier to use than the UI. .git is included, so the repositories must be using git on the backend (whew). I also noticed VITE is used for local development. I also notice they are using bun instead of yarn. The auto update feature is from vite, not really palantir foundry, but that’s fine. The intellisense demo is also not super exciting. That’s just running another typescript build. The steve balmer joke “developers, developers….” was great. Where is the testing framework? I feel like this should have playwright dumped in there somewhere to run tests. Maybe instead they have the AIP discover and run tests?

Palantir Design Principles

Yes it looks like from this video that Palantir uses DDD as one of the main design principles. I wonder if the agents can help you define the model by iterating over the domain concepts like Eric Evans does. But where is Kent Beck Extreme Programming? These Ongology Design principles are really Software Design Principles. I disagree with how the principles are being applied. OCP helps you refactor your software when you discover that you need to extend an existing object. None of the SOLID principles should be used preemptively.