> And I would be describing changes in terms of high level features instead of architectural changes, refactorings and so on, that I do now.
While I haven't worked on any 20yo code base, while working on my projects, I have found that iteratively I am asking to do many of the low-level things like architectural changes and refactorings.
These situations often pop up when I am not getting an expected output, multiple back and forths, specific bugs, continuously flaking tests. I usually then ask it to explain the architecture and what's going on. I add the patterns it's missing or I feel it should consider from next time onwards, to the harness.
It's not the same as pre-llm era but I think this is how things are going to evolve.
Agents are good enough on their own, but they introduce a significant amount of drift.
Simply asking "is this TOOL like SOME_OTHER_TOOL in the codebase?" Is typically enough for the agent to out itself as introducing redundant/refactorable code.
My question is: if an agent knows how to fix a problem in one part of the codebase, and introduces drift in another part of the codebase, is that a problem? If 2+2=4 but so does 3+1=4 and 6-2=4, does this matter? (Math equations are used here to represent similar but varying logic in code)
both your question and your examples are absolutes though. "Is that a problem? yes/no" doesn't survive impact with the real world where the answer is - at best - "yes, but" or "no, although". and how much business logic clearly reduces to a very simple math equation? and even if it does, how many math equations are comprised with a non-toy system?
Is like, this should not take this long, or be this hard, can you explain me what is going on?
And then is when you realize is more complicate than needed, and ask for a refactor. The refactor also takes 5 minutes while you brew coffee, so this is also why I don't buy the anti-doomers saying that someone will need to fix the vibecoded mess, no sir, it will be fixed by vibecoding too while they walk the dogs.
Genuinely asking, why is it considered bad? If it is done right, it will guide the customer better on whether they want something like it. We all see the photos/reviews on google maps before going inside a restaurant.
Pictures on a menu implies that the menu rarely changes - menu creation is expensive and slow - and has standard offerings. This then means that food is likely to be less fresh, less seasonal, and more likely to be precooked in large batches and frozen/reheated. In short, it is a red flag for systemic cooking rather than artisinal cooking.
You find that most higher-class restaurants have a one-page menu, with a soup of the day, 4-7 dishes, and maybe a dessert, with the menu being written once a day and clear about what you get.
I read this quote somewhere: How you do something is how you do everything. I go by this principle in my life. Lately, I have been thinking in how many cases will this be not true.
While I haven't worked on any 20yo code base, while working on my projects, I have found that iteratively I am asking to do many of the low-level things like architectural changes and refactorings.
These situations often pop up when I am not getting an expected output, multiple back and forths, specific bugs, continuously flaking tests. I usually then ask it to explain the architecture and what's going on. I add the patterns it's missing or I feel it should consider from next time onwards, to the harness.
It's not the same as pre-llm era but I think this is how things are going to evolve.
reply