As developers increasingly lean on AI-generated code to build out their software—as they have with open source in the past—they risk introducing critical security failures along the way.
  • kalinux@programming.devEnglish
    1·
    2 hours ago

    “Vibe coding” is just cargo cult programming with prettier syntax highlighting.

    I still think AI’s useful — when it’s treated like a tool, not a replacement. Been experimenting with that in a small side project: VSCoder Copilot

    TL;DR: AI doesn’t make you a dev — it just makes a good dev faster.

    • BilSabab@lemmy.worldOPEnglish
      2·
      2 hours ago

      my only experience with it was for code cleanup - since those tools save me from bitching and moaning from the team - let it rip

    • BilSabab@lemmy.worldOPEnglish
      4·
      9 hours ago

      It has its moments, but you are absolutely right - 25 years ago Wired would’ve torn modern Wired a new one for their clickbait speculative thinkpieces.

  • Hadriscus@jlai.luEnglish
    60·
    1 day ago

    Huh ?

    Open source projects can be inherently insecure, outdated, or at risk of malicious takeover.

    Because proprietary projects are immune to all that ? what is happening here ?

  • Pennomi@lemmy.worldEnglish
    76·
    1 day ago

    Ehhh, I don’t think the comparison they’re making here is right. Leaning on open source software is not just for lazy developers - it’s often the best architectural choice.

    I can’t think of a situation where vibe coding is the best choice except for when speed matters much more than quality, and even then only sometimes.

    • BilSabab@lemmy.worldOPEnglish
      132·
      1 day ago

      It’s only the best option if you are a grifter or grifting the grifter. vibe coding is running roughshod the outsourcing industry. Lots of companies started using it to produce basic throwaway apps and slowly but surely degrades developer’s talent pool. now we get lots of low-grade “developers” who can write prompts and want big bucks for it but can’t pass a mid-level live coding session because their skills are not up the snuff.

      • Pennomi@lemmy.worldEnglish
        71·
        1 day ago

        Sure, but let’s also not discount the idea that a significant percentage of businesses need no more than a single static HTML page for their website. I don’t find it a problem for a person to vibe code that up instead of hiring a real web developer.

        • BilSabab@lemmy.worldOPEnglish
          31·
          1 day ago

          those businesses are not really the target audience for Ukrainian outsourcing companies though. they want the big bucks nice and easy and cut corners more than they should in many cases. On the other hand - there are many Ukrainian small businesses that benefitted greatly from no-code and vibe coding tools that handle their small scale needs - that kind of streamlining helped them focusing on what actually affects their business on the ground

            • BilSabab@lemmy.worldOPEnglish
              1·
              1 day ago

              nowhere, I just relayed my personal observation regarding vibe coding in Ukraine as one of the examples

    • panda_abyss@lemmy.caEnglish
      41·
      1 day ago

      Vibe coding works when you need to say connect to some API and can feed the model a bunch of docs.

      It’s great for very low skill, low maintenance, low risk code that I can easily and reliably regenerate.

      Increasingly coding models are improving at architecture choices, Claude 4.5 vs 4 is way better here. But ultimately it’s inferior to a ginger making those choices.

      It’s also a great debugger and reviewer.

      I used it this weekend to connect to an API and to build a table of constants by just feeding it docs. That was a huge time saver.

      I also used it to try and implement stuff and I gotta say once it hit tricky things it started trying to game it and just say it works.

      • HubertManne@piefed.socialEnglish
        2·
        1 day ago

        thats totally the type of code I have written. granted I really consider it more configuration even if it is code. This is always a thing with jobs. Yes I have written code but no im not really a coder by my definition (writes code over 50% of time at positions). No you don’t really need a coder for this ops role but yeas its fine that it uses continous development and a bit of code needs to be changed and you call it all devops.

        • sugar_in_your_tea@sh.itjust.worksEnglish
          1·
          8 hours ago

          I’m a dev and work with some devOPs, and you nailed my experience with them exactly! Here are some projects I’ve seen them build:

          • open web ui (self-hosted AI) with some custom logic to verify an API key; it’s only available on the VPN/LAN, but IT has rules; basically ended up being a bit of lua in nginx
          • some JS and Python to add some widgets to the app (stuff like reporting issues)
          • random lambdas and other scripts to check server health

          I remember doing all that stuff when I worked at a startup, and it’s nice to just see things get automated.

          • HubertManne@piefed.socialEnglish
            2·
            8 hours ago

            Like half my last role was pretty much automation. Which is sorta good and I guess maybe why devops is a better way to look at it. Back when it was just ops it seemed like they would never give time to get things like automation done.