Comment on Vibe Coding Is the New Open Source—in the Worst Way Possible

pennomi@lemmy.world ⁨2⁩ ⁨days⁩ ago

• BilSabab@lemmy.world ⁨2⁩ ⁨days⁩ 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.

  source

  • pennomi@lemmy.world ⁨2⁩ ⁨days⁩ 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.

    source

    • BilSabab@lemmy.world ⁨2⁩ ⁨days⁩ 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

      source

      • porcoesphino@mander.xyz ⁨2⁩ ⁨days⁩ ago

        When did Ukrainian come into it? I went back to the article but half of it was behind a paywall

        source

        • -> View More Comments
• panda_abyss@lemmy.ca ⁨2⁩ ⁨days⁩ 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.

  source

  • glowie@infosec.pub ⁨2⁩ ⁨days⁩ ago

    GINGERS DO HAVE SOULS

    source

    • BeardedGingerWonder@feddit.uk ⁨11⁩ ⁨hours⁩ ago

      We don’t

      source
  • HubertManne@piefed.social ⁨2⁩ ⁨days⁩ 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.

    source

    • sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨day⁩ 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.

      source

      • HubertManne@piefed.social ⁨1⁩ ⁨day⁩ 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.

        source