been using Claude Code pretty hard for backend work lately and honestly the output is still crazy good. big refactors, moving logic around, cleaning up ugly legacy stuff, it usually handles that better than i expect. but i kept running into the same annoying thing. claude makes decisions fast. sometimes way too fast. a lot of the time the change looks right in the moment, but later i’m staring at the code wondering why we picked that path or where a weird constraint even came from. chat history helps for a bit, then it gets messy. git history doesn’t really explain the thinking either. my flow now is more like: Claude Code for the heavy lifting Cursor for smaller day to day edits Windsurf when i want another pass on a tricky change Copilot for quick cleanup and boring glue work Traycer for writing the spec first so the reasoning is not trapped inside one chat that part made the biggest difference for me. i’m basically trying to separate thinking from generation now. before i let Claude touch anything big, i write down the intent, the boundaries, and what i do not want changed. it sounds slower, but it actually makes Claude better because the task is clearer and future me is not stuck guessing why something exists. for me the real win is not “Claude writes everything.” it is “Claude writes fast, but the structure keeps it from wandering.” curious how other people here are handling this. are you saving prompts, writing specs, or just trusting the model and fixing it later? submitted by /u/nikunjverma11
Originally posted by u/nikunjverma11 on r/ClaudeCode
You must log in or # to comment.