Conversation

Notices

1. Embed this notice
   Boyd Stephen Smith Jr. (boydstephensmithjr@hachyderm.io)'s status on Friday, 08-Aug-2025 23:40:08 JST Boyd Stephen Smith Jr.

   • Thomas 🔭🕹️

   @thomasfuchs This seems to assume the current practice of non-vibe coding has any sort of safety discipline behind it.

   Looking at the CVE rate, as well as the continued unrestricted use of, frankly dangerous, languages like C, C++ and JS, I've not sure vibe coding is any more dangerous.

   The entirely industry needs to be restarted from first principles to actually engineer things.

   I dislike "AI" but the safety of the software output is not one of significant issues.

   We've learned nothing from Therac-25 and Ariane V.

   • Embed this notice
     Poppe :godot: (popcar2@mastodon.gamedev.place)'s status on Friday, 08-Aug-2025 23:58:12 JST Poppe :godot:

     • Thomas 🔭🕹️

     @thomasfuchs I don't like vibe coding either but are we really comparing mildly unstable software with life and death scenarios? Having a vibe coded website render incorrectly isn't going to kill anybody.

   • Embed this notice
     Christine Lemmer-Webber (cwebber@social.coop)'s status on Saturday, 09-Aug-2025 00:33:24 JST Christine Lemmer-Webber

     • Thomas 🔭🕹️

     @thomasfuchs I mean, you probably will have all of those things happen to you without realizing it based on how much proprietary LLM tooling is weaseling its way into many professionals' daily usage

     I've had the surprise "I talked to ChatGPT about it and it said" from multiple non-programming professionals I've talked to about matters I was paying them for