Because the one thing I feel the internet is most lacking is clickbait headlines.
…
Composer is great, it does so much of the heavy lifting for you. But sometimes maybe you’ll have a bunch of repetitive ask/answer jobs to do, and you’ll think “ehh do I really want to pollute my nice clean Composer context with tedium?”
So, very sensibly, you’ll switch to Chat for that, because the tasks are all self-contained and no long-running thought needed. Good. Smart. Keep your strategic Composer context clean for when you need it.
BUT the one side effect of being a heavy Composer user, is: it makes you lazy.
I’m specifically talking about [ Apply ] and [ Accept Changes ].
- You will lose the habit of clicking Apply, and then you’ll wonder why stuff didn’t work, and you’ll think the model or IDE is the problem. I did this. It was not the problem. I was.
- You will switch between Composer and Chat and you’ll forget to Accept Changes before you do, and then you’ll wonder why Chat overwrote all your nice stuff.
For #2, as far as I can tell (at least in the version I’m currently running), failing to Accept before switching over can lead to loss of nice new lines of Composery goodness. Even though un-accepted things are automatically saved, and may even be part of your running app, that doesn’t (it seems) guarantee that they won’t get clobbered when you’re switching around like that. And then you have to figure that out, and try to re-apply things, and it’s a whole headache…
This second issue may be version-specific, and I’d be happy to be wrong about it. But for now that’s my (uncomfortably recent) experience.
Even if I’m wrong, or the issue goes away in a future version, Point #1 still stands.
Composer is so nice, it will make you lazy about clicking [ Apply ] and then you’ll forget to click it when you’re in Chat.
So now Scientists Are Begging You to Stop Doing This One Weird Thing That’s Secretly Destroying the Planet!
thx