1. they aim to deliver product company margins with a consulting-heavy model.
2. your software purchase funds a cadre of "free" FDEs and deployment strategists who customize your install, build a bunch of data pipes/transforms, and talk to people to figure out what all the data means.
This could be a good deal if your tech org is not very competent at integrating your data, or if you have a sudden, short-term need. In the longer term, it's probably cheaper and more effective to develop a competent tech team, modernize the source data systems, and roll your own integration -- but that also requires leaders with long-term vision who are resistant to external hype and pressure.
1. Palantir isn't selling consulting as much as Palantir is selling the confidence you get from buying a name brand. It's the same as paying for McKinsey to provide justification to do what you already want to do.
2. Palantir actually has some good core tech. An in house team can probably do a better job just because the incentives are better aligned, but they'll be starting from behind and have to catch up.
3. LLMs aren't at a level to replace a team of FDEs. Maybe in a couple of years. The role requires too much understanding of the human systems, and too much initiative to keep the ball rolling/acknowledge and deal with real problems.
"In a 2023 blog post, external, Palantir described the challenge of combining data from multiple government systems containing tens of thousands of visa applications and hundreds of thousands of accommodation offers."
This is the kind of thing GDS and other Civil Service departments build all the time, its a completely standard kind of challenge that a small team of Devs (+ supporting staff) from a departments DDAT department does day in and day out.
The output will be open source by default and use existing standards.
Hundreds of thousands of documents is small enough that you can feasibly run a pen and paper office handling them. Especially since most of them do not cross-reference eachother (family applications do, but unrelated families have no such links).
That America's brightest tech minds can't solve this problem is embarrassing. (Never mind the baggage of giving a foreign, potentially adversarial nation access to something as sensitive as residency and visa information.)
I assumed that when the GP said the UK was "giving a foreign, potentially adversarial nation access" the GP meant that the US is that "foreign, potentially adversarial nation"
I can't believe that in our timeline Europe has to think like this, but here we are.
There's not really enough info to know if this is just a coin toss or something more. "Company tries to roll its own system and [saves / loses] money" is just a common story, one way or the other.
For context, the Homes for Ukraine refugee scheme cost 2-3 billion as of 2023. I can't seem to find an updated cost. This cost (from the article) was Palantir working for free for the first 6 months (could they have beat that, time wise?), then awarded 4.5m and 5.5m for two more 12 month terms, and now they're transitioning to something home-grown instead.
> The MHCLG [
Ministry of Housing, Communities and Local Government] said it initially needed a system which could be ready within days but, in seeking a "steadier service", later created an updated platform to meet the programme's longer-term needs and bring down costs.
I basically agree with the MHCLG's reasoning here. It's always worth at least experimenting to see if you can roll your own.
> There's not really enough info to know if this is just a coin toss or something more.
The difference is always having one or two devs who care. Every successful software project I've ever seen has had a few devs who care way more than is healthy
1. they aim to deliver product company margins with a consulting-heavy model.
2. your software purchase funds a cadre of "free" FDEs and deployment strategists who customize your install, build a bunch of data pipes/transforms, and talk to people to figure out what all the data means.
This could be a good deal if your tech org is not very competent at integrating your data, or if you have a sudden, short-term need. In the longer term, it's probably cheaper and more effective to develop a competent tech team, modernize the source data systems, and roll your own integration -- but that also requires leaders with long-term vision who are resistant to external hype and pressure.
1. Palantir isn't selling consulting as much as Palantir is selling the confidence you get from buying a name brand. It's the same as paying for McKinsey to provide justification to do what you already want to do.
2. Palantir actually has some good core tech. An in house team can probably do a better job just because the incentives are better aligned, but they'll be starting from behind and have to catch up.
3. LLMs aren't at a level to replace a team of FDEs. Maybe in a couple of years. The role requires too much understanding of the human systems, and too much initiative to keep the ball rolling/acknowledge and deal with real problems.
This is the kind of thing GDS and other Civil Service departments build all the time, its a completely standard kind of challenge that a small team of Devs (+ supporting staff) from a departments DDAT department does day in and day out.
The output will be open source by default and use existing standards.
That America's brightest tech minds can't solve this problem is embarrassing. (Never mind the baggage of giving a foreign, potentially adversarial nation access to something as sensitive as residency and visa information.)
I can't believe that in our timeline Europe has to think like this, but here we are.
Note that Palantir is an American company that failed to solve this problem well, and introduces an adversarial risk to the UK.
For context, the Homes for Ukraine refugee scheme cost 2-3 billion as of 2023. I can't seem to find an updated cost. This cost (from the article) was Palantir working for free for the first 6 months (could they have beat that, time wise?), then awarded 4.5m and 5.5m for two more 12 month terms, and now they're transitioning to something home-grown instead.
> The MHCLG [ Ministry of Housing, Communities and Local Government] said it initially needed a system which could be ready within days but, in seeking a "steadier service", later created an updated platform to meet the programme's longer-term needs and bring down costs.
I basically agree with the MHCLG's reasoning here. It's always worth at least experimenting to see if you can roll your own.
The difference is always having one or two devs who care. Every successful software project I've ever seen has had a few devs who care way more than is healthy
I would never trust an openly MAGA company.
(FTFY)