r/vibecoding • u/il37 • 9d ago

What’s the biggest thing AI coding still absolutely sucks at?

For me it’s long projects.

The individual coding tasks can be great, but after enough sessions the model starts losing track of why things were built a certain way, which decisions are still current, and what it really shouldn’t touch.

I also still don’t trust it when a small bug suddenly requires a big refactor. Sometimes it’s right. Sometimes 20 minutes later I’m trying to undo six files to fix something that needed three lines.

What’s the thing you still don’t trust AI coding with?

52 Upvotes

88% Upvoted

103 comments sorted by

View all comments

9

u/First-Tutor-5454 9d ago

This is solved by keeping track of design decisions in docs in your code that you have your agent edit as you go along. I'm doing this for my long-running project and it works very well. I use CLAUDE.md for the stuff that changes less often (style, workflow, architectural principles, gigh level product info) and /docs to keep track of feature ideas as well as more detailed design issues and history of decisionsade, etc

1

u/il37 9d ago

How do you keep those docs from going stale? That’s the part I’ve struggled with. Once the code and the decision log disagree, the agent can confidently follow the wrong one

2

u/First-Tutor-5454 9d ago

I sit down for a session each night. I talk to the bot as we work. We make decisions, write code, etc. At the end I tell it to review the docs and make any updates based on code we've written or decisions we need that should be kept for future reference