Just another day I was asking a question how long will it be until we stop looking at AI-generated code - and most replies were in the 5+ years out. I think most - me included - apparently still think in terms of prompt generation and getting that single prompt to LLM to be perfect to do the job.
In the meantime, apparently, with the rise of the agents, that future is already here, and there are some who already harnessed such power. See the video: the author explains their process, and claims that he had not looked into the code for 6+ weeks and only works with the MD specs now.
When preparing recipes for agents - they build entire workflow around managing context, and make them 3-fold: "research, plan, implement", and then he goes into details how they avoid slop and keep mental alignment for developers to keep up with the changes.
Compared to that - I now realize that what I originally built (an AI helper for a terminal: https://github.com/acrotron/aye-chat) is on the "naive" side: prompt until you either get it right from AI or give up and try from the beginning - and with this context generation approach explained I think I will start moving to the agent-based implementation while keeping control plane still in the terminal: current implementation works on smaller code bases but with this approach should be able to cover larger ones as well.
With these techs developing so fast - I think it's just a matter of keeping up with the news - and be aware of what's being done successfully, and unfortunately that's not always easy to do. This one specifically - to let go of code reviews and learning how to work with spec files only - will require mentality change, and it will be a psychological barrier to overcome.
Prompt generation vs. Context generation [video] · HackerTrans
In the meantime, apparently, with the rise of the agents, that future is already here, and there are some who already harnessed such power. See the video: the author explains their process, and claims that he had not looked into the code for 6+ weeks and only works with the MD specs now.
When preparing recipes for agents - they build entire workflow around managing context, and make them 3-fold: "research, plan, implement", and then he goes into details how they avoid slop and keep mental alignment for developers to keep up with the changes.
Compared to that - I now realize that what I originally built (an AI helper for a terminal: https://github.com/acrotron/aye-chat) is on the "naive" side: prompt until you either get it right from AI or give up and try from the beginning - and with this context generation approach explained I think I will start moving to the agent-based implementation while keeping control plane still in the terminal: current implementation works on smaller code bases but with this approach should be able to cover larger ones as well.
With these techs developing so fast - I think it's just a matter of keeping up with the news - and be aware of what's being done successfully, and unfortunately that's not always easy to do. This one specifically - to let go of code reviews and learning how to work with spec files only - will require mentality change, and it will be a psychological barrier to overcome.