620 karma · joined December 8, 2017
“Is this thing dangerous?”
> Nope.
When Claude can do something new, then I think it will be impressive.
Otherwise it’s just piecing together existing examples.
We need a cash/credit alternative, and it’s currently our best shot.
Terms like this one, “alignment”, “low hanging fruit”, all not super accurate but established industry terms.
We could expect failure conditions or assert correct outcomes.
It could become a little library of examples that change over time, as the software changes, granting us peace of mind that everything still works.
A: laziness and cost. It just doesn’t matter the same way that baking code matters, I guess.
So they toss on some cheap anti cheat instead of architecting it safely (expensively.)
And the “right” RC only has to be right enough to solve the issue.
It would be so great to regulate fixing that instead of getting rid of it entirely.
So it’s not being burned, it has a purpose here.
But you still get to scoff, so that’s something.