these tools are cool but oof so many limitations a...
# general
l
these tools are cool but oof so many limitations and problems come with them, the hallucinations and omissions are off the charts, but i digress. 1st issue i see immediatly, no plan is linear as much i would like to one shot my life from A-Z the reality is, evidence and limitations most often than not requires changes to the planning AS WE GO, but the original intent doesnt, which was to fix the tests broken due a refactoring. How does this translate to traycer? I create phases. I can add, subtract etc. However the original query i took time to write that generated all those phases, about a broken test suite etc and a database, after the first phase was created and the evidence collected made the whole next phases automated queries irrrelevant, which now require to be rewritten. This defeats imo the whole automation workflow you guys are going after with yolo. This wont apply to every scenario ofc specially when a project is new, but as things start to complicate. ETHER A or B. A) i rewrite some queries given the new information (which ok not a big deal, except for yolo mode, or B there must be some type of functionality that on new evidence/reviewing some of the queries ON THE WHOLE CHAIN must readapt, still would need supervision by a human anyways)