Sorry you're struggling. There are tons of resources out there from people who've been through the same pain and built up techniques to mitigate them. Matt Pocock's YouTube channel is one good starting place, there are many others. One key tip though is - you own the architecture of your application. If your files have become bloated over several rounds of LLM-generated code, that is primarily your responsibility to observe and push back on that, to ensure your repo as a brief but firm AGENTS.md or CLAUDE.md to describe architectural non-negotiables and some kind of /code-review skill that you give to a second agent to review the first agent's work against those standards. Worried about LLM changes introducing regressions? That's why you have a test suite, and you read what the agent changes to ensure the tests themselves are still checking for correct behaviour.
AI coding is a nightmare. Am I the only one experiencing this?
11–20 of 62 posts
Re: AI coding is a nightmare. Am I the only one experiencing this?
#12I don't have those experiences with Codex (5.5 xhigh).
Re: AI coding is a nightmare. Am I the only one experiencing this?
#13Sounds like more of a rant than a question and for that you get a ranty reply. Ask the AI how to improve your results.
The post is decidedly a question. It is a forum, people come to interact with humans and exchange opinions.
Re: AI coding is a nightmare. Am I the only one experiencing this?
#14What a pitiful state of programming affairs ... Just couple of years ago we have been discussing new libraries and tech architectures and algos. Today we discuss how to "shoehorn" some 3rd party crap into making your life miserable. Best case scenario: it will get smart(er) and replace you. (Yeah, the cope of "owning your architecture") Worst case: you redo all that shite by hand and still get replaced.
And the tragedy?
We ceased being programmers. We don't even qualify as code monkeys anymore ...
Re: AI coding is a nightmare. Am I the only one experiencing this?
#15The most painful part is the “add instead of change/delete” habit. The real test for AI coding assistants isn’twhether they can generate code, but whether they can understand the existing system, reuse the right abstraction,remove bad code, and own the whole call chain after the change.
Re: AI coding is a nightmare. Am I the only one experiencing this?
#16You are right, my solution is to implement real world software engineering process, something closer to a real Software engineering team.I split multi agents into one repo and gives them different tasks"requirements check, product/spec, architecture, coding, review, tests/evals, and overall management.
Scope adjudication is extremely important in vibe coding, or agent can easily break your whole system with not applicable features.
Re: AI coding is a nightmare. Am I the only one experiencing this?
#17[flagged]
Re: AI coding is a nightmare. Am I the only one experiencing this?
#18How did you find way to fix, i have the same issue, been trying to implement rules above it, repo focused memory, etc and still having the same issue over, as you say it always prefer create new code or files instead or modifying the existing ones then end up creatomg problems that wasnt there before…
Re: AI coding is a nightmare. Am I the only one experiencing this?
#19Spec driven development can help some, even for brownfield projects. You can have an LLM swallow up your entire project and spit out a spec, and then review that yourself.
For any issue, start a brand new context, point it to the spec, explain the issue and explain if it's a regression.
Also on it might seem like an obvious one, the more test coverage you have, the more your llm can tell if something has broken or if there's been a regression without needing to eat up context.
All of these things can help but there's no perfect solution.
Re: AI coding is a nightmare. Am I the only one experiencing this?
#20[flagged]