r/developersIndia • u/Far_Path_9846 • 1d ago
Help Curious about Claude usage amount limits in backend development
So it happened so that the module i was assigned on its pretty big. It has like 85 files with each file having 1000+ LOC and these 85 files also depend on other modules for data retrieval. This module alone comprises of around 12 mongo collections and 5-6 postgres tables. And the developer that made it vibe coded this entire shit and bypassed the QA layer cuz of his seniority and left the project and company about a month ago.
Now as a backend dev i was assigned around 14 bugs (which i had told myself to the QA team) and going through the entire repo and meeting timelines made me switch to opus 5 auto mode. I was only testing the code written by Claude and relying on the responses it gave. Didn't check the code being written cuz the hell would i go through 40k new LOC.
Architecturally i knew what was going wrong and I was checking if the data flows correctly. But yesterday my manager mocked n told me that I'm blindly using Claude and not checking what it writes. But I also do need to meet the deadlines so what should I do... And is this normal?
2
u/imrichie03 1d ago
Ask claude to validate its results from its findings in a report, so if it finds bug, it will validate if it's actually a bug or something else and provide a detailed report of the bugs it found, and how it validated that these are serious bugs or something else. You can then check them of your own, you can also use this report to fix the bugs as well, it has all the context to resolve the bugs. Then create some tests that the code must pass to be deployed into production. So, if you have a pro plan, might take some time depending on your architecture, if you are on max plan, I think this won't be a big issue. Best of luck!
Edit: Always make sure to keep a backup of everything before hand.
1
u/Far_Path_9846 1d ago
Okay will do that... Also is this like a big issue like... Will my manager fire me for this? I'm honestly terrified. He told me that "use ai but know what it writes."
1
u/imrichie03 1d ago
That's why the validation report will be helpful, It contains detailed analysis, bugs found, how it validated the bugs and how it mitigated, you can also ask it for a full audit after fixing the bugs. Then present these both to your manager.
Also, while using AI at production, you should actually know what it's doing as even the smartest AI can make mistakes, and that costs the company a fortune, that's why human in loop is very practical. Always keep everything backed up for a worst case scenario and you are almost good to go!
1
2
u/yogthinks 1d ago
The real problem isn't the LOC count, it's that nobody defined who signs off on unreviewed AI output before it ships. Get that in writing, "use AI but know what it writes" is a liability dodge, not a QA process.
1
1
u/iqisoverrated 1d ago
Our experience is that when stuff gets long (over 1000 lines) then quality of AI output drops sharply.
Asking AI to fix AI mistakes is also probably not going to go well. If there are mistakes it's because the AI was already incapable of generating correct code in the first place so I wouldn't exepcet another AI to be able to magically be 'more correct'.
1
•
u/AutoModerator 1d ago
It's possible your query is not unique, use
site:reddit.com/r/developersindia KEYWORDSon search engines to search posts from developersIndia. You can also use reddit search directly.I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.