I generally love claude and have it used it in the past to build simple apps, but I am generally deeply involved with the decision making and will write a fair amount of the code at first and then have Claude clean it up and make recommendations. Recently I started building this much more complex app with a react/ts frontend and a fast api post gres backend. It’s sort of a side project at work so I can’t really sink the time into it and really my knowledge of typescript and react is limited. Beyond providing some basic ground rules about repo structure and state management, I’ve been pretty hands off. I feel my brain sort clouding up and while it’s exciting to see results so quickly I feel like i will pay for it in the long run. What’s your approach in these situations? Take a break and have Claude walk you through the architecture? Just keep plugging ahead? I find opus is not as great as I would have hoped but I’m not sure if my prompting approach is wrong or what; like basic things with css and state seem to slip through. Is this just the nature of dev now? Not fully understanding things and just accepting it so long as it works and has some generally maintainable structure? The frontend is typescript and react with zustand for state mgmt and tailwind css. Also not a true dev by training. Got my start in gis, but moved more into development recently submitted by /u/Sen_ElizabethWarren
Originally posted by u/Sen_ElizabethWarren on r/ClaudeCode