Yeah you guys have to pay attention to the state of the overall economy. We are in the credit-crunch phase of a recession. The funny money has ran out and infinite loans are no longer available. These companies have to find way to pay their debt now
Working with a team of SREs using LLMs to troubleshoot production issues and holy shit - the rate at which it uses that exact language and comes to completely fabricated or absurd conclusions is close to 80-90%
Responses like these are a big part of what convinces me that the hysteria around Palantir is unfounded. I see broad claims about how the company is violating privacy, going to overthrow democracy, etc. but when pushed for details, most people just fall back on basic partisanship.
How does it not make sense? Companies all over the world trust their proprietary data with Palantir platforms. There’s no way they would do this if they thought Palantir was actually sharing data without their approval. If they were found out to have done this, companies would cease to trust Palantir and stop working with them
Yeah no way are people developing actual applications. They’re developing one off apps, tools and websites. The amount of robustness a usable application with actual purpose requires is exactly where LLMs fall apart.
I’m not a naysayer by any means and at this point use Llms all day for many purpose. But it is undeniable that the exact moment complexity reaches a certain threshold, LLMs need more and more guidance and specific implementation details to make worthwhile improvements. This same complexity threshold is where real world functionality lives.
lol you guys are being too nice. Building CRUD apps is just implementing business logic by gluing APIs together, there is nothing to understand except the business domain, which is only done through exposure, because business logic is random. And then the APIs which are all essentially a kludge because of the shifting business logic.
Understanding low level code puts you on entirely different level because you can reason about a problem using logic and how systems operate.
No disrespect to any crud devs here but from my personal experience they just know a particular implementation of their domain and rarely even consider how the code base even operates as a whole
> lol you guys are being too nice. Building CRUD apps is just implementing business logic by gluing APIs together, there is nothing to understand except the business domain, which is only done through exposure, because business logic is random.
It isn't "random", a as business process develop over time to various business/customer/regulatory needs. The business process evolves over time typically.
When you take a business process, you are often formalising it. The fact that you have no appreciation of this, tells me you don't really understand what you are talking about.
> Understanding low level code puts you on entirely different level because you can reason about a problem using logic and how systems operate.
You have to do this in high level languages as well. It isn't something that only low level devs do. In fact to be able to write any good code you need to understand the problem domain.
> No disrespect to any crud devs here but from my personal experience they just know a particular implementation of their domain and rarely even consider how the code base even operates as a whole
You are literally disrespecting them by saying this. It is also false, what you are describing is developers having deal with incomplete/poor specifications and poor documentation. BTW this is rampant through the industry. I wanted to do some stuff yesterday with Docker and Go, the documentation is non-existant.
Wanting and being interested are not things in physical reality. We are also talking about an organization and not some aspiring teenager.
If someone wants something , the only measure of their interest and desire is how much resources and time they allocate to it. We’re not measuring Sam Altmans deepest desires and fantasies here
reply