Comment by browningstreet

They're neck and neck for me, in terms of PRDs, coding, and web searching. CC built the bulk of my current project, I did a lot of analysis of it with Antigravity (the interface is esp good for reviewing/commenting on long .md output files) and then, after building a simple roadmap of v2 features, OpenCode + Kimi was the most aggressive about running in a fairly autonomous manner and finishing the items on said roadmap. OC was also pretty hardcore about misinterpreting a limit I expressed earlier in one context as a limitation in another context -- which was fine, I'd rather say "no, really, you can go do that, I'm giving you permission and here's what I meant before" than find out it was too brazen.

It's a lot like managing two experienced mid- to sr- engineers each of whom have slightly different personalities and intro/extro verted personalities. CC has more personality but OC wants to race. They can both code, but for disparate tasks you might pick the personality and posture of one person over the other.

I find myself picking daily tasks based on which of the tools I'm in the mood to sit with. But across a few days I sit with all three.

turnsout 2 days ago

Oh interesting—how do you find OpenCode vs CC? I'll check it out. And I'll try to get a version of this assistant in a form I could share publicly.

Reply View 1 reply

browningstreet 2 days ago

They're neck and neck for me, in terms of PRDs, coding, and web searching. CC built the bulk of my current project, I did a lot of analysis of it with Antigravity (the interface is esp good for reviewing/commenting on long .md output files) and then, after building a simple roadmap of v2 features, OpenCode + Kimi was the most aggressive about running in a fairly autonomous manner and finishing the items on said roadmap. OC was also pretty hardcore about misinterpreting a limit I expressed earlier in one context as a limitation in another context -- which was fine, I'd rather say "no, really, you can go do that, I'm giving you permission and here's what I meant before" than find out it was too brazen.
It's a lot like managing two experienced mid- to sr- engineers each of whom have slightly different personalities and intro/extro verted personalities. CC has more personality but OC wants to race. They can both code, but for disparate tasks you might pick the personality and posture of one person over the other.
I find myself picking daily tasks based on which of the tools I'm in the mood to sit with. But across a few days I sit with all three.

Reply View | 0 replies