Post #3942091

@cocoaphony@mastodon.social anecdotally, I never used the term “one shot” until I ran Fable through some personal projects. It seems to get many details “good enough” without a lot of oversight. It is slow. Fable seems to better infer under-specified requirements and makes good guesses the first time. Opus is effective but will sometimes break stuff that was previously working. It gets “distracted” if you don’t manage context? I’ve seen people suggest planning with Fable and executing with Opus. Hope to try that approach some day on bigger problems. I do try to use the simplest/cheapest/most focused model available. I’m writing one-off Swift prototypes, not solving hugely complicated problems.