I remembered saying how I had an issue with my entire application because I decided to add a new feature and the whole code just go messed up, and that I had two options?
I ended going with my first option because I was already far into the project and so I had to dig deeper to find out what was going on.
Ways you can dig deeper is
- To pay attention to the files the agent or assistant are constantly making changes leaving them stuck in that loop compared to where you think the actual errors are coming from and try to redirect it to the right part.
- You might notice that step 1 worked for one part
where you think the error is coming from
And other parts are still having errors, just do the same thing because now the agent or assistant is not wasting it’s time and your time looking somewhere irrelevant to the actual problem
These are what I did I didn’t have to result to my second option. And after immediately fixing the issues I connected my repl to GitHub and I plan on making a commit after every new changes.
I haven’t made any changes yet to make a new commit though, I’ve just been taking a sigh of relief after this one.
And if you don’t know what I’m talking about with your repl and GitHub just check out this post here by @robinbobinpopin what a champ in this forum btw Tips on Rollback and Version Control
I’m still trying to figure out what to do next after a commit and such error occurs again ( that’s your whole code being messed up) how to roll back to the last working state.
Untill next time
Hopefully this helps anyone in a similar situation not to give up if you are willing to spend a little more time and dig deeper into the issue rather than always prompting the agent to fix it.