191–200 of 224 posts
I did something similar to a local company here in Spain. Not medical, but a small insurance company. Believe it or not, yes, they vibecoded their CRM. I sent them an email and they threatened to sue me. I was a bit in shock from such dumb response, but I guess some people only learn the hard way, so I filed a report to the AEPD (Data protection agency in Spain) for starters, known to be brutal. I've also sent them a…
I saw something very similar a few months ago. It was a web app vibe coded by a surgeon. It worked, but they did not have an index .html file in the root web directory and they would routinely zip up all of the source code which contained all the database connection strings, API credentials, AWS credentials, etc.) and place the backup in the root web directory. They would also dump the database to that folder (for ba…
interesting, so the ai got the hard stuff right. password hashing, schema design, fine. it fumbled the stuff that isn't really "coding" knowledge, feels more like an operational intuition? backup folder sitting in web root isn't a security question, it's a "have you ever been burned before" question, and surgeon hadn't. so they didn't ask and the model didn't cover it, imo that's the actual pattern. the model secures…
Every other field that's figured out high stakes failure models eventually landed on the same solution - make sure two people that understand the details are looking at it - pilots have copilots surgeons with checklists and nuclear plants have independent verification. Software was always the exception, cause when it broke it mostly just broke for you, vibe coding is not going to change the equation, it barely remove…
We do have code reviews for pull requests. But on average I would guess there is great amount of complacency there. I suppose old proper QA phase was best answer we had. But that is expensive and slow.
Earlier quoted context omitted.
Doesn't require Jira but yes, specification-first is the way to get better (albeit still not reliably good) results out of AI tools. Some people may call this "design-first" or "architecture-first". The point is really to think through what is being built before asking AI to write the implementation (i.e. code), and to review the code to make sure it matches the intended design. Most people run into problems (with or…
I used to manually curate a whole set of .md files for specs, implementation logs, docs, etc. I operated like this for a year. In the end, I realized that I was rolling my own crappy version of Jira. One of the key improvements for me when using Jira was that it has well defined patterns for all of these things, and Claude knows all about the various types of Jira tickets, and the patterns to use them. Also, the spec…
Interesting how unquestioning the responses are that this isn’t engagement bait
Earlier quoted context omitted.
Negligence depends on what you believe to be true. If you're being told "this is possible and the AI will do it properly you don't have to worry" then it's not negligence really - on the part of the person who believes what they are told. For the rest of us it is about being put under pressure by managers who don't understand whether to believe what you say or what they read about vibe coding on some linked-in post.…
> "this is possible and the AI will do it properly you don't have to worry" then it's not negligence really Then that's lack of due diligence and and any manager is forcing you to ignore that, you should report them to compliance team. You cannot blame everyone else and bear no responsibility for your actions. If you decide to vibe code blindly and ignore all the laws and standards, then that was your decision and yo…
They watch your AI usage and pressure you to use more. They tell you that "of course you must check the code" but of course if you do then they can start telling you your performance isn't good enough. "Fred is much faster than you" and of course Fred says he checks everything but does he really? To do code reviews he just uses an AI anyhow so nobody catches what the AI doesn't catch. If you check his code carefully in a review and bring up a lot of questions (which he cannot answer because he doesn't know) then you're being "difficult" and dragging the team down.
Is this what I'm experiencing now? perhaps about 70% of it but I can see how it goes. There are lots of companies out there with poor development practices who think that AI will save them. They don't want to prioritise "quality" although they shout about this a lot. They think that somehow they don't deserve to have quality issues if they prioritise speed and features and don't bother to fix any problem until it causes downtime.
Please forgive my cynical view. I have simply had some bad experiences. It's not always easy to do what is right even when it's fully in the company's own best interest.
Earlier quoted context omitted.
I used to manually curate a whole set of .md files for specs, implementation logs, docs, etc. I operated like this for a year. In the end, I realized that I was rolling my own crappy version of Jira. One of the key improvements for me when using Jira was that it has well defined patterns for all of these things, and Claude knows all about the various types of Jira tickets, and the patterns to use them. Also, the spec…
I self-host OpenProject - free and a little better than Jira.
Have you been using Claude Code/whichever tool you use, to read and write from OpenProject directly? I do like self-hosting data like this. I used to self-host Jira back in the day.
Earlier quoted context omitted.
You don't want some gatekeeping on who will be doing surgery on you? You do obviously, and medical malpractice is a good thing if there is a problem. Why don't you want the software engineer building your pacemaker or your medical CRM (or any other job where your immediate security is engaged) to have the same kind of verification and consequences for their actions?
It's mostly the problem of required regulations, so no we don't want mandatory gatekeeeping on surgeons as this is for example leading to doctor shortages It's fine to set up voluntary standards and choose surgeons you think live up to those So we want to enable more people to be able to create for example pacemakers because of things like Linus's law, "Given enough eyeballs, all bugs are shallow". If we exclude "non…
Why shouldn't any self taught "software engineer" be liable for damages they caused due to negligence? If we had to sign off builds of critical components (like a pacemaker to stay with the analogy), there would be way more pushback against malpractice in the development process. Of course not all software projects require that level of rigor, but for medical stuff and I'm sure a lot of other fields, it should be mandatory to have at least one qualified engineer that is ultimately responsible.
You guys realise this is AI slop on AI slop, right?
This is reality now, what do you want?
I don't think solving this is all that complicated, at least for now. It isn't like it's currently difficult to tell what is and isn't LLM word salad, though that will likely change in the future, but by then the argument will involve whether it really matters or not. But for now, when 80% of the submissions are LLM garbage and it really is garbage, it's pretty jarring.
(In not a lawyer and so I might be mistaken about this; Especially the level of intentionality might be a factor)