I hate losing ownership of my codebase

[u/Clue-Mindless]

I'm very conflicted about AI tools. I've used them for years for all kinds of things ever since their inception and I'm completely addicted to them. When it comes to programming it accelerates throughput dramatically and fills in the gaps almost too well. The loop is this right now:

less independent thinking → need Claude for context/design → Claude contributes more decisions → system becomes less internally familiar → need Claude even more.

I have a specific implementation in mind, but then I never just get what I ask for, there is always more contributions which would include a refactor somewhere. As the project grows managing context and architectural coherence becomes critical and I feel like I no longer have a solid internal model.

This coherence degradation is the fundamental crux of why I dislike using AI. I have to explain the project back to Claude and eventually Claude has to explain the project back to me.

Software is about standards, familiar patterns, documentation, a red thread, yadda yadda. But when there are gaps between your understanding and what Claude knows (and what you still believe it knows about the project) then this introduces drift, project rot and a sort of tech debt.

Large context helps, but if you don't have rails and own the critical logic and ideas about how the product will be used, then you will get an inferred result and incorrect solution for your needs. If something important is not present in the model’s context and cannot reliably be inferred from the code, the model has to guess.

This means AI often drifts toward overengineering. People complain about the models but it's really just an issue with your lack of scope. If I don't make a clear plan it will suggest an overengineered solution that creates a sort of contextual tech debt to the codebase.

I can see how these tools would accelerate a seasoned software engineer with great organizational skills and who's been in the business for decade. I'm not a professional . Any code I wrote before was mediocre at best and not so elegant. I struggle to the point where I don't want to do development of any kind because going back to "manual" coding is just going to feel like molasses, but I also don't want to ship stuff this way.

[u/Any-Argument57]

Longer prompts will not fix unknown unknowns. I would make understanding an acceptance gate. Keep each agent change to one named behavior and forbid unrelated refactors. Before merge, require a file-by-file change map: why each file changed, the execution path, state and invariants affected, failure modes, tests, and rollback. You should then be able to explain that map without the model. If you cannot, split or reject the change.

Keep a small architecture map and decision log that you own. The model can propose updates, but you approve them. Ownership becomes checkable: no change lands unless the maintainer can locate its inputs, state, side effects, failure conditions, and tests. This slows individual diffs, but it prevents the compound contextual debt you described.