• Mika@piefed.ca
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    25
    ·
    3 days ago

    Very cringe thing to do when the whole industry jumps on LLM-automation wagon. This way you filter out people who actually do stuff professionally.

    Good to know though. Would avoid.

      • Mika@piefed.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        There is nothing unethical in the goal to simplify development. The only unethical thing here is how giant American closed source AI corpos try to trample the competition to become monopoly in providing essential tools.

        AIs need to be open source and hardware to run AIs needs to be obtainable.

        • cloudskater@piefed.blahaj.zone
          link
          fedilink
          English
          arrow-up
          1
          ·
          21 hours ago

          Except the ethical issues of LLMs are inherent to them. Get rid of the corporate aspect will not ease the most pressing issues with LLMs, as they are baked in.

    • Matty_r@programming.dev
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      3 days ago

      The only acceptable use in the industry is using it as a code analysis tool - vibe-coding is not.

      • Mika@piefed.ca
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        7
        ·
        3 days ago

        Why though? Aside from blind hate, good written JIRA stories are almost oneshot now in many occasions. You can spend more mental energy on logic correctness rather than translation of requirements into code.

        Not only it is faster, but you can deliver greater quality faster. Slopware is a result of trying to crank the dev speed to the max without following proper sdlc with proper dod.

        • Kacarott@aussie.zone
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 days ago

          The company I work at has fully embraced vibe coding, so from my experience: it did seem faster at first, but also the amount of regressions and new bugs being introduced has gone up dramatically, and so the overall workflow has stabilised to be roughly just as fast as before AI, but now almost all mental energy is going into QA and reviewing. From the customer perspective, they saw lots of new progress initially, but have now been frustrated by constantly finding things broken or buggy.

          And all this is at a company which has entire teams dedicated to trying to improve AI-based workflows and tools to make them more reliable.

          So no. From someone in the field, quality has dropped a lot, and speed is only increased if you close your eyes and ignore all the tech-debt being created.

          • Mika@piefed.ca
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            2 days ago

            Your devs do QA, not a dedicated team?

            Unit tests, snapshot tests, UI tests?