For some tasks, there is no amount of "steering" that will produce sensible code. The model needs to be sufficiently capable as a baseline; this is the "intent" that people are referring to with Fable.
That doesn’t sound like the “it hammers until it’s done”-type of intent.
Just last night Fable decided to get into a rabbit hole of debugging a database driver issue by packet sniffing the network traffic instead of just adding debug statements to the code. Definitely needed steering, and I don’t know many people whose first intuition would be to use pcap when they have a segfault.
Overengineering is the name of the game with Fable. Sometimes you don't want that, sometimes you really do, especially as a researcher. It's a very nice tool to have around for those special tasks.
Just last night Fable decided to get into a rabbit hole of debugging a database driver issue by packet sniffing the network traffic instead of just adding debug statements to the code. Definitely needed steering, and I don’t know many people whose first intuition would be to use pcap when they have a segfault.