Aram J. French | website

Transcript

A single panel comic with a malformed, slightly damaged, yet freshly built home in the background. In the foreground, a man in a hard hat and a reflective vest is speaking to another man, presumably the buyer, saying, “It’s called vibe construction. I’m not even a contractor! Pretty soon all buildings will be made this way.”

  • NeatNit@discuss.tchncs.de
    4·
    2 hours ago

    I’ve long said (well before AI) that we must have similar kinds of regulation for software, especially software that is used as infrastructure. This includes ~all social media, operating systems obviously, productivity software, shopping websites/apps… It’s all the wild west, with so many dark patterns and predatory tactics, all of which regulation would ban. Software engineers would have to be certified and personally responsible for their design, just like civil engineers.

    It would have to be balanced somehow with software freedom. I don’t want to add any barriers for hobbyists and bedroom programmers just wanting to play around with code and share it. But at the same time, I see that barriers are sorely needed for everyone else.

    • Holytimes@sh.itjust.works
      4·
      1 hour ago

      Hobbyist carpenters also don’t have to deal with like 99% of the regulations around buildings.

      You can just go make a chair, or a table. Frankly if code is going to be used in a serious large scale project it shouldn’t be the realm of hobbyists and if it does somehow end up like that they should be held to same strict code as the professionals.

    • smiletolerantly@awful.systems
      1·
      2 hours ago

      How about only apply to non-FOSS software? Most hobby projects used not just by the author altend to be FOSS, and businesses can decide to go FOSS, making their software independently auditable by anyone, or go through certification.

      I guess there’s a danger of a campaign to re-brand FOSS as “uncertified” then…