LmCast :: Stay tuned in

My business partner sent a 5K vibe-coded PR that he didn't even test

Recorded: Sept. 8, 2026, 8:09 a.m.

Original Summarized

My business partner sent a 5K vibe-coded PR that he didn't even test – YHCJ

YHCJ

Home Blog

My business partner sent a 5K vibe-coded PR that he didn't even test

08 Sep, 2026

The whole payments backend module, which I specifically told him to work together with me (I do frontend), was vibe-coded by him in one single day.
How nice, to not have to discuss with the human being who will be using your code and knows what he wants, and instead work with a sycophantic "yes man" AI right?
All 5,236 additions to the Github PR, including a documentation that is so blatant of AI redundancies (for example, saying that an error returns "400" on the API).
I understand that AI doesn't know that I know what a 400 is, but my friend should at least read that document and know better.
So here's the sad part. I understand y'all vibe-coding features and being 10x engineer and way faster than me.
But I just went to test the PR...
It doesn't work.
He didn't even TRY the endpoints.
It takes two minutes to run the endpoints that Don Claudio so happily added to Bruno.
Two minutes.
He clearly didn't read the documentation as there was a lot of stuff missing. Stupid explanations about a "returns 400 on error" but missing info on where to get API keys.
And I specifically told him, when we started this project, that he should be very careful of falling into the AI trap of letting his cognitive abilities decline.
"Yes, yes, no worries man I know what I'm doing".
Famous last words.
Well, as much as people lose all their muscle by been bed-ridden, he's lost all his brain by being AI Assisted™️.
THIS is what I am so against when people use AI for everything.
And I know, some of you will say "but that ain't me, haha, I can sit in my couch and watch TV all day and not exercise and keep all my muscle!"
Well wait until you go play a basketball game with your pals and you'll realize you're out of breath in two minutes.
I know it's a losing battle for the few of us who learned to program and still program mostly by hand because we love the amount of stimulation it brings our brains.
My friend used to be one of those people. But I think there's almost nobody left.
Those days are gone, and I'm still grieving, but I think this is my very last battle.
After this project, I'm done. I might turn into a yoga teacher.

 

Powered by Bear ʕ•ᴥ•ʔ

The author expresses significant frustration regarding a process where a business partner utilized an AI to "vibe-code" the entire payments backend module in a single day without performing any testing. The core complaint revolves around outsourcing fundamental development tasks, which the author views as circumventing the necessary human element of collaboration and understanding user requirements. This approach led to substantial additions to the GitHub pull request, including documentation that relied on superficial AI redundancy, such as stating an error returns "400" without providing contextual details on how to manage those errors or accessing necessary API keys.

The failure to test the resulting code immediately exposed critical flaws. The author notes that running the endpoints, even those added by another party, took two minutes, highlighting a lack of proper functionality. Furthermore, the documentation suffered from missing essential information, such as explanations regarding the location of API keys, despite the AI's inclusion of superficial error messages.

The author emphasized that relying on AI assistance risks cognitive decline among programmers. The experience suggests that while AI can generate code quickly, it lacks the necessary contextual understanding and critical judgment that a human developer possesses, which is crucial for ensuring the functionality and maintainability of complex systems. The author contrasts this modern reliance on AI with the traditional learning process where hands-on programming provided essential mental stimulation and skill development. This sentiment reflects an underlying concern about how increased dependency on automated tools may erode the innate cognitive abilities developed through manual problem-solving in the field of software engineering.