3 ms·
I've used it. Honestly it's the same place as goose and aider ... it tries to DIY its own solutions too often as opposed to using existing robust libraries, wri
by kristopolous 1y ago
I've used it. Honestly it's the same place as goose and aider ... it tries to DIY its own solutions too often as opposed to using existing robust libraries, writes inflexible code where simple piped commands would do, and basically Katamari Damacies the problem into a complicated sprawl that doesn't work.
- danenania 1y agoThanks, I appreciate the feedback. I think the reason you tend to see these same kinds of problems across tools is that you are running up against the reasoning limitations of the underlying models. I see my goal as trying to push that horizon out as far possible, and I think Plandex pushes it significantly farther than most other tools, but you do of course still run into those limitations. That said, I think even setting aside improvements to the underlying models, there's a lot of potential to improve on these issues. I think they're all basically addressable at current capability levels, though they are difficult problems. It's what I'm personally most excited to work on.
- kristopolous 1y agoHonestly, I think it simply becomes the wrong modality at a certain level of engagement with any problem. When human developing a project successfully you engage in different collective behaviors throughout the process. That's why the scrum/agile stuff that tries to normalize it doesn't actually work very well. On computers, relationships are workflows and you need to do a dance of fluid relationships to use AI effectively throughout the execution process - otherwise that's why you either abandon it after you get to some point or you feel like you're just wasting time.
- danenania 1y agoYou're right. I think the solution essentially boils down to modeling those other modalities and incorporating them into the agent.