My business partner sent a 5K vibe-coded PR that he didn't even test
A developer recounts how his business partner vibe-coded the entire payments backend in one day, producing a 5,236-line PR with redundant AI-generated docs and untested endpoints. The author, who had warned against relying on AI, finds the code doesn't work and feels his partner's cognitive decline mirrors muscle atrophy. Frustrated, he contemplates quitting programming after this project.
Well, as much as people lose all their muscle by been bed-ridden, he's lost all his brain by being AI Assisted™️.
- cladopa
AI is not the problem here, but the difference in deep beliefs of the company founders.
When I had partners in my business I studied them first deeply like I was going to marry them because I WAS going to marry them!
You should agree on your values or else the company will go nowhere. One founder will raw one way and the other the opposite making the boat to stay in the same place.
I have a software company and the opposite problem: I am obsessive about testing and meta programming. We write way more testing code than code, we automate everything with meta programming.
It was clear several times that we tested and automated way more than necessary. We automated things that only used once for example(although we used later multiple times on other projects).
So we had not the usual problems than companies have like bloat or security vulnerabilities but we had the problem of having software that was was super expensive because we did double or triple the code than the competition with tests that developers hated(they are boring to write). Our software took also way more time to market.
Companies love to buy the cheapest they can today and tomorrow we will see, so that put us in a difficult position. It was specially hard at first, but then this principles gave us an edge(because most companies would compromise early and not reap the benefits later).
Had I a business partner with a different mindset and beliefs, it would have been impossible to me not to change course of the boat […]
- socketcluster
This is literally the recipe for the coming software apocalypse.
Just watch the software engineers who say "Let's be careful" lose their jobs and get replaced by non-technical vibe-coders churning out 10K lines of dirty insecure, unmaintainable code per day... Ticking time bomb.
I swear, good engineers are going to move to North Korea to monetize because of the amount and size of 'opportunities' this will create.
It seems so far-fetched but that's the direction it seems to be heading.
- Valodim
Doesn't sound like AI is necessarily the root the problem. If he's not the person to test, iterate, and deliver quality with AI, he probably wouldn't be without it. You just figured it out sooner.
Or, if you have reason to believe he's got what it takes - treat it like an leaving opportunity, give him room to make mistakes. This is, ime, what a rookie AI user mistake looks like.
It is easy to get carried away by the momentum. Many have fallen into that trap, not all are irredeemably bad software engineers.
- yhcj
OP and long time lurker here, I'm desperate and looking for honest-to-god advice on what to do.
I am one of those neurodivergent people who loves programming because it gives me the right stimulation.
I also enjoy drawing, gardening, and exercise.
I don't own a car because I love walking, and such.
So I'm wondering if it's time to call it quits with programming (for a living).
Luckily I have some savings and I have other interests from years of doing random jobs and businesses, and as much as I love programming, especially with others, I think very few of us still want to program.
I'm like the Last Samurai of programming while everyone is using AI-assisted gattling guns.
Is it time to let go?
- dreieinsvier
In my opinion, software engineering was never mainly about programming.
Programming is a rather small part of the software engineering cycle.
Programming by hand is one way (it also works with AI), to make decisions. Decisions about scalability, maintainability and sanity of your software.
And still this will pay off!
To me it sounds as if he is a very bad software engineer.