[CamperBob2]

The most powerful way to use Fable in particular seems to be to pit it against Sol as a reviewer (or, I suppose, vice versa.) After going back and forth a half-dozen times, the result tends to be pretty much bulletproof.

What's somewhat disturbing is just how much Fable's code really does benefit from the review. It tends to leave a lot of low-hanging fruit, and you can see it getting kind of impatient when repeatedly called on it.

[apt-apt-apt-apt]

"We've now re-explored this question three times. While there were small differences along the way, one more would be pathological. Perhaps meditation or therapy would be more fitting."

This is basically how Fable told me to get therapy.

[Foobar8568]

The problem with that approach, the code becomes over-complex, over-engineered and more often than not, it will take a specific point and iterate over it.

It's still what I do 90% of the case until I feel it's good enough for my usage.

[divyekapoor]

What are you using to put Fable and Sol on each other?

[CamperBob2]

I just keep them in separate directories and use .bat files to copy files back and forth. Crude but effective enough.

1) Fable generates updated .c sources and .md design documents in myproj_fab

2) A batch file in myproj_sol copies the updated files from myproj_fab to myproj_sol

3) I tell Codex to "Review updated files, write findings to review.md"

4) Sol rips Fable a new one, usually

5) Another batch file copies review.md back to myproj_fab, where I tell Claude Code "See review.md"

I don't want to automate it any more than that, because I'll get lazy, stop watching the tennis match, and miss something important. Which will probably happen anyway...