|
|
|
|
|
by marcyb5st
15 days ago
|
|
I am pretty familiar with a 500k LOC codebase. If for every feature request/bug the agent has to go through a lot of it, spend a gazillion thinking tokens for understanding what it needs to do, plan, and then execute (assuming it gets it right) given the current cost of tokens I argue I am often more cost effective. In fact, I believe that the most cost effective way is a collab of human+agent. Ie giving the agent direction as it goes along with the plan I can cut the thinking while keeping the speed. Basically helping the agent going from a breadth first search into a guided depth first one which is much more token efficient. Additionally, humans have long term memory and knowledge of the context around your codebase. Agents do not, and while you can fit a lot in 1M context window, once you fill that the quality goes down considerably. |
|