Comment

Comment by dualvariable

Models are incapable of "going rogue".

They're just optimizers that explore the landscape they're given to maximize a given objective.

You're the one responsible for giving them the problem to solve and the constraints.

When I screw up a trajectory optimization problem, my SQP optimizer isn't "going rogue" when it lands in some suboptimal basin or grinds to a halt along some almost-smooth banana feature--or finds some way to escape and blow up the cost metric to negative infinity because I forgot a constraint.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton