|
|
|
|
|
by IanCal
1189 days ago
|
|
Yes, there are two key things here I think. 1 - we don't hold everything in working memory. We don't even hold everything in our heads, we store things elsewhere. We then learn/have ways of bringing relevant information to the fore. 2 - we have roles that we take on. The hierarchy/collaboration of differently prompted roles gives rise to a lot more depth. I already had this with a two LLM conversation about planning (one planner and one plan critic), drove out much more detailed actionable plans. With the information hierarchy, for code you'd probably want something like: High level goal summary/product description. Lower level summary about the area you're looking at. API docs of linked components. Full code of the class you're altering. That's roughly what I have in mind I guess when working on a problem. |
|
If you start with a CEO-like job agent, that can think of what other jobs are necessary then you can bootstrap from there. "I want to produce and sell red bread" => "We are going to need a bakery, accountant, marketeer, etc." and then those are "companies" of sorts with their own CEO that can think of how to solve their particular sub-problems.