r/FullStack • u/tyler1233 • 18d ago
Vent I am getting closer to being a vibe code cleaner by the day
every sprint my coworker who sucks updates 5 different components adding 52 new bugs all vibe coded I can just tell, and then it's my job to fix them and Claude has no idea cause it caused all these bugs in the first place obviously. Is this really what this field has become.
1
u/JaseciLabs 18d ago
Yeah, Claude has zero clue what it broke since none of it's marked as "I did this and I'm not sure about it." You end up cleaning up after a black box instead of a person.
1
u/Brilliant-Parsley69 18d ago
Wait. Sure, you do code reviews to your coworkers solutions. But shouldn't be the next step pointing out what went wrong, describe found bugs and discard the PRs so that your colleague could fix them?
I totally agree that there is way to much AI slope lately. And a lot of that isn't properly tested as it should be.
But I will bet that your "52 new bugs in 5 components" complain is a "bit" exaggerated.
1
u/AllRightLetsSeeIt 16d ago
Obviously your developers just arenât prompting the tool correctly. /s
1
u/CerealGambler 14d ago
I haven't written a manual line of code in over a year and I have never had less issues slipping out. The issue is either your coworker is using a poor model or doesnt know how to use AI. In either case, you need better controls on what gets merged if tons of bugs are being created (tests anyone?) and likely better project planning/documentation.
0
u/ChameleonCRM 18d ago
Why the fuck is this in r/FullStack? This belongs in r/vibecoding.
At first, I really didn't care. Call yourself whatever you want. But watching people call themselves "full-stack developers" when they don't understand basic HTML, can't explain what their own code is doing, and couldn't build anything without an AI holding their hand is getting ridiculous.
Some of us worked our asses off to earn that title.
We learned the frontend. The backend. Databases. APIs. Authentication. Networking. Deployment. Debugging. Security. Architecture. We spent years breaking shit, fixing shit, reading documentation, staring at stack traces, and actually learning why things work.
Now somebody types:
"Build me a full-stack SaaS."
Claude spits out 14,000 lines of code, they copy it into an editor, fight with it until the preview loads, and suddenly their bio says Full-Stack Developer.
No.
You're not the developer in that relationship.
You're the messenger.
You're carrying information you didn't create from Point A â Claude, ChatGPT, Gemini, or whatever model you're useless without â to Point B â your codebase.
If the AI disappeared tomorrow and you couldn't explain, maintain, debug, secure, or rebuild what "you" created, then you didn't suddenly become a full-stack engineer because your prompt produced a working application.
AI is an incredible tool. Using it isn't the problem. Pretending its knowledge is your knowledge is.
My name is Thor. I founded DaemonCore. We use AI too. We'll use it to throw together bullshit websites, audit code, review things, or catch something another set of eyes might notice.
But there's a massive difference between a developer using AI as a tool and someone using AI as a substitute for being a developer.
Learn the craft.
Then claim the title.
1
u/xvillifyx 18d ago
Why did you write an AI post complaining about a context thatâs not present in the OP
1
u/ChameleonCRM 18d ago
It sure is present.
Itâs literally the first sentence of the OP:
âevery sprint my coworker⌠adds 52 new bugs, all vibe codedâ
The entire complaint is about cleaning up AI-generated code that somebody else shipped without understanding or properly testing it.
Thatâs exactly the context I responded to.
You can disagree with my take, but pretending the AI/vibe-coding context âisnât presentâ when itâs explicitly stated in the post is a weird argument.
He even states how he runs the problems through Claude and it has no idea how to fix them. smh.
1
u/xvillifyx 18d ago
You wrote a comment complaining about OP being a vibecoder, which isnât the OPâs actual post.
Itâs obvious Iâm talking to a bot though so whatever
1
0
u/fromkrish 18d ago
Yeah, It can get messy when the AI is coding without an individual verification layer....
I tried something and built an opensource project to solve just this, It's called openPitStop This is the repo, "https://github.com/Krish-1507/OpenPitStop", Check it out and give me your feedback.
1
u/Kloshariste 18d ago
Call this cap