773 karma · joined February 9, 2021
Of course Humans can make errors when translating that to English. But if you’ve read any amount of Claudish it should be obvious that interpolating the code to documentation with an LLM typically produces a significantly worse result in almost every way. Except for superficially “sounding” correct.
Having some way to unlock an iPhone doesn’t at all imply it must be done in a way that reduces security, or trusts the average user with upholding it.
Use your imagination. They could require you to have an apple developer account. Or visit an apple store. Or even limit it to a special developer unlocked iPhone flavor.
Apple spends a huge amount of effort maintaining two different operating systems for what is pretty much the same machine under the hood. Don’t be naive and try to rationalize their bad behavior. They clearly just want to maintain their lucrative software distribution monopoly.
80% incoherent narration of random numbers, all down to the 1’s place so it looks super duper precise and impressive if you squint and don’t think too hard, like the “author” seems to have done.
To reach a more optimal solution, significant human steering is reqiured for every tiny decision. It’s the same as how early models needed hand holding on the basics, playing out again in the finer details. Human experts need to inject “eureka moments” from the outside.
And no feedback loop that I’ve tried has been able to conjure an understanding of these finer details that, as far as I can tell, just aren’t represented in the weights.
Modeling the basics of software engineering was easy, since things like writing code that passes some tests is easy to RL. But for anything not easily RL-able, we’ve basically ran out of human generated tokens to distill from.
Without some breakthrough in generalization, I remain unconvinced that we’ll be able to model the finer details of software engineering by looping the existing training corpus back into itself. Garbage in, garbage out.
For example, finding a loophole to keep it difficult unsubscribe. Or making it easy to unsubscribe, but adding an egregious cancellation fee to all subscriptions.
Another good example is when NYC passed minimum pay laws for delivery drivers, and the big delivery companies immediately all colluded to hide the normal tip screen behind a bunch of submenus (until eventually forced to change it back).
Is it really unclear to you what the intent is here? What specifically about the rule do you think is ambiguous?
But you need some understanding of the underlying complexity to appreciate compression. We’ve all seen and tasted stuff, so a beautiful painting or a great pizza are easy to recognize.
Programming is tricky because the complexity is hidden. To laypeople it’s confusing, “why is this simple feature so complicated??” Even to other programmers it’s often non obvious. Someone could have spent days factoring the solution to a difficult problem down from 1000s to 10s of LoC, but unless you've also wrestled with that particular problem, it just looks like simple code anyone could have written. But really that’s the beauty of it. Programming is a massive space to explore that’s hard to fully comprehend.
And yet you still just get slop.
It’s all just surface level complexity with no intention behind it. A clumsy approximation at best.
Facebook has broken its promises about user data many times before. I don't buy anything they say about Muse, and nobody in their right mind should. Unless they’re getting paid to, of course.
Aside, if “a skill file organizing purchase history in markdown format” is the only thing you took away from that thread, you might want to take a closer look.
As a sanity check, I’d highly recommend trying out your own line of reasoning in cases which you think you might feel differently about. For example, imagine it's instead a certain authoritarian state saying "obey the Party or get blacklisted as a national security threat."
It might feel good in the moment, like "yeah, Anthropic, don't tell the military what to do," because you agree with this particular call. But the government doesn't give that power back, and you might not be so happy about the next way it gets used.
A mutually agreed upon "you may not use our product for X or Y purpose" in a contract clearly doesn't pose any such risk.
Makes sense for GP locally, I guess, but globally we’re all worse off when nobody is motivated to break free from the path of least resistance.
I say just let them duke it out. After a decade of regulatory capture and enshittification, it’s nice to see some actual competition again.