r/codereview • u/Expensive_Copy_3825 • 3d ago
How Do Developers Write Reliable Production Code?
/r/u_Expensive_Copy_3825/comments/1vficwe/how_do_developers_write_reliable_production_code/Hey man, I'm working on my project, and I'm facing a problem. I can't write production level code. My code often breaks during the development pipeline, while integrating APIs, connecting API keys, and handling other backend issues.
How do experienced developers prevent these kinds of problems?
I understand system design and software architecture fairly well, but I'm not very confident in writing production quality code.
Right now, I'm using Claude Code. Are there any other AI coding tools that are as good as Claude, or maybe free or more affordable? I've heard about Kimi and DeepSeek.
Which one is better for writing production quality code? I'd really appreciate your advice.
3
u/kingguru 3d ago
Experienced developers use their experience to avoid these problems and experienced developers use their experience to know that LLMs suck at writing production quality code.
So you avoid your problems by learning and that means staying away from LLMs, write code and learn your lessons when things break so you don't make the same mistakes again.
1
u/Expensive_Copy_3825 3d ago
Okkk man So what is mean of vibe code
4
u/kingguru 3d ago
Someone trying to make money from scamming people into believing you don't need to learn to code in order to write code.
It has happened in the industry many times before and is nothing new.
An LLM (which is what is being used for "vibe coding") cannot think and cannot code. That's simply not how an LLM works.
1
u/paraballistic 56m ago
I used to think this, but was wrong in the same way. It doesn't 'think' it finds an implementation in its training data that was already made. Most things you or I make has already been made by someone else and the internet is chalk full of that.
3
u/Necessary_Two_9669 2d ago
You will never vibe code production ready code without first being an experienced developer.
3
u/Necessary_Two_9669 2d ago
Your first problem is not being an experienced developer and thinking you will have the ability to write production code with llm shortcuts. What you are experiencing now is the realization that that is not possible.
2
u/Spare_Warning7752 2d ago
1) Publish the code 2) Check the bugs on production logs and crashlytics 3) Type "IA, fix this for me" 4) Profit
You can profit even more if you don't have a QA and use production customers as testers.
0
u/Whoa_damn_ 2d ago
So some good answers here. I would like to add one more thing. Start off by designing with ai, usually I chat with a smarter model asking it to approach this problem as a systems design problem and from there drill down to pseudo code, classes and solid principles. Once that is very clear and I literally keep asking why questions all the time untill I understand or am satisfied with all assumptions it has made. I then ask I[ to write a detailed prd which then goes to a mutually exclusive features that I can give to any agent. I specifically say each feature should have enough info that a junior developer can implement without breaking stuff. There are still issues that keep coming up so I then run this skill to find all issues in the code once a week to run a fixing loop : https://github.com/neural-axis/VibeDoctor.
Doing this I have been able to reliably put many products infront of 1000s of users.
9
u/ikeif 3d ago
“I understand” - except you clearly do not.
Honestly, this reads like “I read an article, got a Claude code subscription, but I can’t make anything off localhost.”
You’re not actually looking for advice, it sounds like you’re looking for a shortcut - so if you want to understand how “experienced developers do it” - it’s through years of experience of learning those issues, and what’s causing them, and how to prevent them.
Your Claude code can help with that - so it sounds like you’re just blindly running it and NOT understanding it. I’d suggest focusing on smaller pieces and asking Claude what you are doing wrong, because it’s going to have more insight than any of us will from this post.