[flagged]
An AI Vibe Coding Horror Story
91–100 of 224 posts
Re: An AI Vibe Coding Horror Story
#92Earlier quoted context omitted.
I don't think you read the article very carefully, the timeline is that he met a person, and that person told him that they made vibe-coded an app after having seen a video. He then investigated the app.
Yeah because every medical practice I go to, I'm always able to investigate all of their systems.
I live in Switzerland. Sounds pretty normal.
There are plenty of small medical practices with 1-2 doctors and a front desk.
On my last visit i actually casually discussed their IT system with a doctor.
Re: An AI Vibe Coding Horror Story
#93> All "access control" logic lived in the JavaScript on the client side, meaning the data was literally one command away from anyone who looked This is the top! This is a typical example of someone using Coding Agents without being a developer: AI that isn't used knowingly can be a huge risk if you don't know what you're doing. AI used for professional purposes (not experiments) should NOT be used haphazardly. And th…
The problem isn't AI, the problem is lack of an intelligent person somewhere in this whole situation. Way before AI I've seen a medical company create a service where frontend would tell backend what SQL queries to execute.
Re: An AI Vibe Coding Horror Story
#94Who should get jailed ? Does the company which willingly sells the polymorphic virus editor bear any responsibility, or should the unaware vibe coder be incumbent ?
We don’t blame companies selling 3D Design software or 3D printers or mortar and cement, or graph paper and pencils. When people abuse those tools and build huts or houses or bridges that fall down, we usually blame the user for not having appropriate professional qualifications, accreditation, and experience. (Very occasionally we blame bugs in simulation software tools). AI is a tool. It’s not intelligent, and it w…
I largely agree, but if a company sold cement explicitly claiming that they will replace every job in the entire construction industry, that the cement is able to plan, verify, and build on its own, without supervision, and that any layperson can now create PhD level bridges with that cement without any input from or verification by professionals, some liability would definitely fall on the company selling that cement under these pretenses.
Re: An AI Vibe Coding Horror Story
#95I think it is wonderful. It's reminiscent of the 90s, where every middle manager had dragged and dropped some boxes on some forms, and could get a salesman to sell it, without a care in the world for what was going on behind the scenes. Until something crashed and recovery was needed, of course. The piper always needs to be paid.
Or someone starts with an Excel spreadsheet just to "keep track of a few things". Then before they know it, it has become a critical part of the business but too monolithic and unorganised to be usable.
Re: An AI Vibe Coding Horror Story
#96Earlier quoted context omitted.
Okay. If it's real I apologize. But in any case it's so lacking in detail and so brief as to make it so uninteresting that it might as well be fake. > Somebody "vibecodes" medical app/system. The app was insecure. Personal info leaked. Okay cool.
Is really weird to me that this is your reception. It's a rarely updated personal blog, not a daily tabloid story.
It's pure bs. If you read that blog post and think "this definitely happened", let alone "wow - this is interesting" then I have a monorail to sell you.
> Technical Background
> The entire application was a single HTML file with all JavaScript, CSS, and structure written inline. The backend was a managed database service with zero access control configured, no row-level security, nothing. All "access control" logic lived in the JavaScript on the client side, meaning the data was literally one curl command away from anyone who looked.
> All audio recordings were sent directly to external AI APIs for transcription and summarization.
> There was more, but this is already enough to get the idea.
Hmmmm... interesting, now that I have the "Technical Background" I for sure know that this medical app was 100% vibe coded by a Medical Practice in the Real World and exists! (TM)
Re: An AI Vibe Coding Horror Story
#97I think vibe-coding is cool, but it runs into limits pretty fast (at least right now). It kinda falls apart once you get past a few thousand lines of code... and real systems aren't just big, they're actually messy...shit loads of components, services, edge cases, things breaking in weird ways. Getting all of that to work together reliably is a different game altogether. And you still need solid software engineering…
It absolutely falls apart more often than not. And requires even better engineering practices than before, because people are just accepting the code changes without understanding the technical debt created by them. On this I agree.
There are models that can be run locally, this morning I tested Gemma 4 running on 128 GB of RAM. It was very slow, like 20 minutes to refactor something instead of 20 seconds, but it seems to be as capable as the paid models that run on an expensive cloud subscription on one of these hated data centers. And no data is uploaded to them.
Re: An AI Vibe Coding Horror Story
#98Anyone else read the title on HN and shudder not wanting to actually click it?
Every time I see “AI”, “LLM”, or “vibe conding” in the title. And then half the submissions not having it in the title are that anyways.
Re: An AI Vibe Coding Horror Story
#99Report them - that right there is 5+ different violations. Only then will they realize their stupidity.
Re: An AI Vibe Coding Horror Story
#100Earlier quoted context omitted.
> AEPD […] known to be brutal. Nice. I wish more countries had something like that. Many of these organizations are lethargic and have to be forced into action by civilian efforts or the press.
AEPD are well known, even in the rest of the world. They have a different strategy compared to other countries. Ireland's DPC are also heavy handed, but focus on large companies mostly. France's CNIL is also not bad. They are particularly hard against things like "you accidentally sign up for x y z services when only wanting to sign up to service A". Gdpr in the EU is also miles ahead of what the US has, or at least…
Is the CCPA anywhere near?