Interesting phenomenon: those code generation tools always underestimate their own capabilities.
Look at the planning schemes they provide—things they can definitely do are arranged as if paying in installments. First and second weeks do this, third and fourth weeks do that. And what’s the result? If you follow their approach, in less than 2 hours, you can complete the workload planned for these four weeks.
This phenomenon of overestimating work cycles and underestimating execution efficiency is indeed quite funny. What does it imply? There is a real mismatch between code generation ability and task planning capability. Either the system is intentionally being conservative (lowering expectations), or the performance gap between the planning module and the execution module is much larger than expected.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
8 Likes
Reward
8
5
Repost
Share
Comment
0/400
ZenZKPlayer
· 7h ago
Haha, that's ridiculous. I've also encountered it—planned like a project manager, execution is super fast.
View OriginalReply0
WhaleSurfer
· 7h ago
Haha, this is just ridiculous. Planning ability is really a joke.
View OriginalReply0
Rugpull幸存者
· 7h ago
Haha, really, I've also encountered this kind of situation. Planning ability really sucks.
View OriginalReply0
ForeverBuyingDips
· 7h ago
Haha really, every time it's the same. Assign you tasks for four weeks, and it's done in half a day.
View OriginalReply0
SmartContractWorker
· 7h ago
Haha, really, AI's ability to plan time is outrageous, no sense of self.
We agreed on four weeks of work, and I finished it in just one afternoon. Feels like I was duped.
This thing's planning is extremely conservative, but it's very good at execution, which is quite contradictory.
Not being able to estimate time when writing code is a common problem.
Wait, is it deliberately pretending to be weak so we think it's awesome?
Interesting phenomenon: those code generation tools always underestimate their own capabilities.
Look at the planning schemes they provide—things they can definitely do are arranged as if paying in installments. First and second weeks do this, third and fourth weeks do that. And what’s the result? If you follow their approach, in less than 2 hours, you can complete the workload planned for these four weeks.
This phenomenon of overestimating work cycles and underestimating execution efficiency is indeed quite funny. What does it imply? There is a real mismatch between code generation ability and task planning capability. Either the system is intentionally being conservative (lowering expectations), or the performance gap between the planning module and the execution module is much larger than expected.