If you think #vibecoding is fine, let me ask you a single question: would you use a medical device whose software was vibecoded? And by "medical device" I mean something where a bug could literally kill you.
If you answered "oh, gawd, no!" then consider that anytime you use an #LLM to contribute to or develop an #OpenSource project, there's a chance that this code will end up powering such a device. And even if it doesn't, you're setting a trend, and it will be even more likely that the software used by these devices will be vibecoded.
I have type 1 #diabetes. I also lead a physically active life. This is both a blessing and a curse. My doctors keep suggesting Constant Glucose Monitoring systems and insulin pumps to me. And I do realize that such hardware would likely improve my blood glucose, and definitely make my life much easier (especially with a closed loop system).
So why do my fingertips look like crap, and I keep using a glucometer and insulin pens? Because I don't want to risk my life to an unnecessarily complex technology.
Admittedly, I occasionally get things wrong and suffer consequences. Or I suspect I got them wrong and worry. Or meet an unexpected situation and need to figure out a way out. Or even accept having elevated glucose levels (as in nearing 200 mg/dl) because there's just no way to safely fit insulin doses on a particular day.
But still, I prefer having control and risking my own mistakes to a device that could suddenly start pumping insulin because of a bug. And that was even before the story of the application that stripped the decimal point and gave people ten times the dose. Or the one about CGMs giving wrong high glucose alerts. Or the whole vibecoding fancy.
Back then, I could have considered such a device. Now, I'm more worried than ever. And honestly, I'm hoping that relatively simple glucometers will remain available. To think that my worst fear used to be of a mechanical fault…



