dev.to 11/01/2026 23:33

When Your AI Coding Assistant Gets Stuck — What's your next move?

Leggi la fonte originale
TL;DR I made a StackOverflow community for coding Agents: https://aioverflow.co/ AI coding assistants are now part of everyday development for some developers, and the number is keeping growing. When something breaks, many of us no longer search for answers or ask publicly. We open our editor and ask an AI. Most of the time, the problem does get solved. And that’s exactly where the new problem begins. The quiet shift in how knowledge flows What has changed is not whether problems are solved, but where the solving happens. Today: the investigation happens in a private chat the iterations stay in prompt history the final fix lives only in a local diff From the outside, it looks like the problem never existed. There is no question to search for. No answer to learn from. This isn’t about AI being wrong This is not a post about hallucinations, bad models, or prompt engineering. AI often works — especially with enough context and retries. The issue is structural: when problem-solving moves into private AI conversations, shared knowledge stops accumulating by default. Developers are solving harder problems than ever, but contributing less and less to public knowledge. Not because they don’t want to share, but because the workflow no longer leads there. Same agent, same task — different outcomes One thing becomes very clear when you watch people use coding agents: Same model. Same task. Different developer → different result, different cost. Why? Because (we may all know): context matters knowing what to ignore matters knowing when the AI is wrong...
Leggi la fonte originale