| ▲ | redmalang 2 hours ago | ||||||||||||||||||||||||||||||||||
Us too! Hardware is very interesting - I find in fact that 'smart' (aka expensive) models can overthink complex hardware state machines and end up doing atrocious code because it will try to handle every possible edge case (unbidden, mind you). What has worked very well is harvesting and aggregating lessons and feeding this automatically into our pi sessions, this allows the models which listen to instructions to avoid a lot of time burning tokens on internal dialogue to ascertain the nature of reality.. but the expensive ones: a) they dont listen b) they ironically know too much! | |||||||||||||||||||||||||||||||||||
| ▲ | jacquesm 2 hours ago | parent [-] | ||||||||||||||||||||||||||||||||||
Funny, I wonder how many people are retracing the same pathways. Another interesting one: asking for reboots or resets to start from a 'known state' even though this will not change a thing. But it's a quick path out of the trouble spot that might just work so why not try it. I've added the following line: "The hardware is on a spaceship and is impossible to access by an operator and for some reason they forgot to include reset logic, so we have to work with what we've got.". I've been gaslit by AI so often I figure I can return the favor without penalty. | |||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||