Hello! I’m developing my project using Claude. It’s medium-sized native utility for Mac (for now, crossplatform later). It’s not much in terms of functionality but the logic is quite complex. I don’t review code usually, at maximum I glance at it. Instead I rely on a dashboard of metrics which let me peek what’s going on inside. These include sizes of built app, LoC, high-level dependencies between modules, spilled user data, external writes, etc. Everything works better then I expected. Bugs are basically caught right on the spot. My utility includes diagnostic logs which describe all significant data flows in app and when I meet the bug, it just reviews my logs and fixes it – almost always without my any intervention. However, I noticed that his coding organization was sometimes questionable. For example, he put user-facing strings, which should be reused and localized, not in the reusable core part, but in platform-specific part. It was not the single time it put things into a place they clearly don’t belong to. App worked either way but this is something I, as an ex-coder, consider technical debt. So the question is: what do you think, how much technical debt can a model bear until it starts throttling and producing nonsense? Have you ever hit such limit? submitted by /u/Brilliant-Ocelot1536
Originally posted by u/Brilliant-Ocelot1536 on r/ClaudeCode
You must log in or # to comment.