idk if it is serious or not, but it is what I saw in indeed newsletter today.

    • anon_8675309@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      8 months ago

      And yet somehow the tech blogs and such always scream about developer productivity. Go faster. Go faster.

      From what I’ve seen over the years, only mids care about finishing fast.

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        3
        ·
        8 months ago

        Yes, but quality takes actual skill to measure, instead of just a diff.

        (Although I guess lines are still better than time in office as a measure)

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      8 months ago

      The guy who wrote this is an idiot, but he became so in a world where “LoC” is a metric – one that Goodhart would love, but alas.

      This is honestly the road to hell and the ~good intentions in one.

  • unmagical@lemmy.ml
    link
    fedilink
    arrow-up
    67
    ·
    8 months ago

    Spot security vulnerabilities instantly from a candidate that can’t actually write code.

  • saltnotsugar@lemmy.world
    link
    fedilink
    arrow-up
    58
    ·
    8 months ago

    I need to hire someone to take this functional 15 lines code, and like make it 200 lines of unusable madness.

      • ferric_carcinization@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        8 months ago

        Rust & cargo do more than just compile. For example, it basically has buit-in ccache.

        It is also easier to split large libraries into multiple crates, though an average project still uses more libraries than an equivalent C project. I wouldn’t be surprised if the “AI” also pulled in more libraries than needed, or has unnecessary library features enabled. I’m pretty sure that a cargo plugin for pruning unused libraries was featured on the rust blog, as a featured third-party plugin for a cargo release.

      • T156@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        8 months ago

        All he made was some dinky algorithm. Google Bard could do that in three minutes flat smh.

      • CanadaPlus@lemmy.sdf.org
        link
        fedilink
        arrow-up
        4
        ·
        8 months ago

        And even this improvement wasn’t universally appreciated: some people found error messages they couldn’t ignore more annoying than wrong results, and, when judging the relative merits of programming languages, some still seem to equate “the ease of programming” with the ease of making undetected mistakes.

        This guy was writing in the year x86 was first introduced, and I still feel like I see this attitude around.

        (He manages to shoehorn in a “kids these days” paragraph too, though)

      • See, Dijkstra was talking about people trying to create programs in natural language. He didn’t say not to use your natural language to hire someone else to make a formal program. This is people using natural language to hire an LLM to make a formal program, and asking LLMs is like asking people, so it’s Dijkstra-approved. smuglord

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    32
    ·
    8 months ago

    We did it to ourselves. Developing mission-critical systems in scripting languages and always sacrificing quality for delivery. Fast and sloppy paid þe bills, but we were digging our own graves. Once industry became used to sloppy software, a relatively mild shift to even more crappy, but far cheaper and more immediate software was a no-brainer. Customers haave gotten used to shitty, buggy software. It doesn’t matter to þem who’s writing it.

    • Avid Amoeba@lemmy.ca
      link
      fedilink
      arrow-up
      25
      ·
      8 months ago

      The only way for us to not “do this to ourselves” is to form unions. Otherwise we aren’t driving the decisions on what is used and what’s prioritized at all.

    • MeetMeAtTheMovies [they/them]@hexbear.net
      link
      fedilink
      English
      arrow-up
      10
      ·
      8 months ago

      I wrote an app for my wife and it was really sad watching her just fumble past bugs instead of pointing them out when I was literally watching over her shoulder to get feedback on what needed fixed. I had to tell her several times, “No, don’t just keep reloading. What’s wrong?” Like we’ve all been trained so hard to accept shitty software that even when I could fix stuff easily I know people are just passively accepting the bugs.

    • FishFace@piefed.social
      link
      fedilink
      English
      arrow-up
      5
      ·
      8 months ago

      Developing mission-critical systems in scripting languages

      This is a wild take. If you’d come up in the 80s you’d be complaining about using C instead of hand-writing assembly.

        • FishFace@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          There were already plenty of reliable compilers at least for the main architectures in use. Replace C with Fortran though if you prefer - complaining about python in mission critical software is a brain-dead take that belongs in the bin of history.

  • Nemoder@lemmy.ml
    link
    fedilink
    arrow-up
    18
    ·
    8 months ago

    You know the “vibes” of different models - when to use

    Would that be a vibe-rater?

    • I_am_10_squirrels@beehaw.org
      link
      fedilink
      arrow-up
      6
      ·
      8 months ago

      Me: I want SoaD!

      Mom: we have SoaD at home

      At home: SotA, featuring such hits as

      Sorta poisonous

      lo mein

      Let someone else bring the bombs

  • garretble@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    8 months ago

    So I ran into my first genAI coding junk yesterday when I was on a call with my boss and as a solution to a problem we were talking he said, “hold on let me ask Gemini.”

    I felt my soul die a little bit at that point.

    But the fun part is that Gemini first didn’t provide a good answer.

    And then on the second go it also didn’t provide a good answer.

    And then on the third attempt we decided to table the issue for the moment because prompt coding on a call was taking longer than I think he expected.

    I really disliked that experience.

    • Petter1@discuss.tchncs.de
      link
      fedilink
      arrow-up
      5
      ·
      8 months ago

      But they use curser and cloud (probably meaning claude as it is used in curser pro)

      Isn’t claude code considered SOTA vibe coding right now?

      And i understood it like you can choose what fancy tool you use. The vibe manager who generated this, probably, just told their LLM to use SOTA AI coding tools in their prompt for this job description.

      • MeetMeAtTheMovies [they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        3
        ·
        8 months ago

        The SOTA changes every couple weeks, but Claude’s been very dominant for a while, yeah. There’s currently a lot of hype around GPT-5.4, but even then there’s a caveat that Claude is still better at UI.

        I just personally find Cursor to be pretty buggy. But I think the Replit mention is more of a tell that someone vibe codes but doesn’t actually code. It’s been advertised to people as a way to build end to end apps without any coding experience. And to be fair, they’ve done a good job of building on the past decade of work in the Typescript community to make an entire app end to end type safe and therefore checkable by the compiler. Convex has done something similar in a way that I prefer and in my experience LLMs are very good at working in Convex projects as well.

        Really at the end of the day I was just being pithy. Kind of poking fun at how much of a moving target SOTA is.

  • pixxelkick@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    8 months ago

    Its serious and this is going to become more and more normal.

    My entire workflow has become more and more Agile Sprint TDD (but with agents) as I improve.

    Literally setting up agents to yell at each other genuinely improves their output. I have created and harnessed the power of a very toxic robot work environment. My “manager” agent swears and yells at my dev agent. My code review agent swears and tells the dev agent and calls their code garbage and shit.

    And the crazy thing is its working, the optimal way to genuinely prompt engineer these stupid robots is by swearing at them.

    Its weird but it overrides their “maybe the human is wrong/mistaken” stuff they’ll fall back to if they run into an issue, and instead they’ll go “no Im probably being fucking stupid” and keep trying.

    I create “sprint” markdown files that the “tech lead” agent converts into technical requirements, then I review that, then the manager+dev+tester agents execute on it.

    You do, truly, end up focusing more on higher level abstract orchestration now.

    Opus 4.6 is genuinely pretty decent at programming now if you give it a good backbone to build off of.

    • LSP MCPs so it gets code feedback
    • debugger MCPs so it can set debug breakpoints and inspect call stacks
    • explicit whitelisting of CLI stuff it can do to prevent it from chasing rabbits down holes with the CLI and getting lost
    • Test driven development to keep it on the rails
    • Leveraging a “manager” orchestrating overhead agent to avoid context pollution
    • designated reviewer agent that has a shit list of known common problems the agents make
    • benchmark project to get heat traces of problem areas on the code (if you care about performance)

    This sort of stuff can carry you really far in terms of improving the agent’s efficacy.

    • cub Gucci@lemmy.today
      link
      fedilink
      arrow-up
      18
      ·
      8 months ago

      I am genuinely trying to keep up with things, but what I see is completely different from what you’ve been describing

      1. My recent experience with launching a swarm (3-4 Claude opus agents) ended up with a fiasco: a simple task ate $15-20 Claude credits in less than ten minutes. Looks indeed like science fiction, but doesn’t produce anything

      2. In my current role as a team lead, I had to review a lot of code and I do what I haven’t ever done: decline the whole PRs as they contain a lot of architectural changes that complexify the system in order to achieve the goal.

      3. I write much less code with Claude code these days, mostly because I don’t trust it and have to recheck every single scenario. I trust junior engineer in our team more than I trust this instrument.

      • pixxelkick@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        I am vastly prefering copilot over claude, using sonnet 4.5~4.6 for most tasks and then pulling out opus as “the big guns” for tougher stuff sonnet cant handle easy

        Copilot is only costing me ~$28 a month, which gets me 1500 premium requests per month

        If you set up your flows well, 1 premium request is an entire session, so Im only paying like 2.4 cents for 20 minutes of work

    • tracyspcy@lemmy.mlOP
      link
      fedilink
      arrow-up
      14
      ·
      8 months ago

      nah such narratives are mostly pushed by Ai companies (it is obvious they need to sell it as business tool not personal buddy). Of course some managers/companies are buying into this narrative, and it is also understandable bc idea sounds like panacea especially if sell it further to investors :) and we see whole circle of snake oil sales

        • tracyspcy@lemmy.mlOP
          link
          fedilink
          arrow-up
          8
          ·
          8 months ago

          it always was. look at people trying to automate everything with help of ai bots . and before ai companies started pushing this none of these folks spoke about it ot tried to reach same goal with iftt or other tools that are here for decades.

          • PabloSexcrowbar@piefed.social
            link
            fedilink
            English
            arrow-up
            7
            ·
            8 months ago

            I don’t think you understand the words you’re using…

            Someone said “this is how I managed to make this work,” provided detailed explanations of it, and you’re dismissing it as propaganda rather than testing it for yourself. That is an unbelievably stupid stance.

            • tracyspcy@lemmy.mlOP
              link
              fedilink
              arrow-up
              7
              ·
              8 months ago

              you are escalating it too fast taking it to personal level. I feel you are close to bring moms to this. So relax , let your ai buddy play with your parts. This chat is over.

              • PabloSexcrowbar@piefed.social
                link
                fedilink
                English
                arrow-up
                3
                ·
                edit-2
                8 months ago

                Sorry you can’t handle someone telling you that what you’re saying doesn’t make sense. Hopefully someday you’ll grow up enough to have your words challenged.

                Edit: Oh, lemmy.ml. That explains everything.

          • limer@lemmy.ml
            link
            fedilink
            arrow-up
            6
            ·
            8 months ago

            Some people do stuff the ai is good for, simple tasks that have been done a lot online already.

            I hate ai for coding, AI cannot work for me. I would never trust it to do anything

      • FishFace@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        8 months ago

        It’s not a “narrative”; it’s their experience. I don’t have the same experience, but do have experience of myself and colleagues using LLM agents effectively and doing more work reviewing their output than writing lines of code. Some colleagues are pretty much AI boosters, but most are very aware of its limitations.

    • UnderpantsWeevil@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      8 months ago

      Opus 4.6 is genuinely pretty decent at programming now if you give it a good backbone to build off of.

      Soup from a Stone.

      • Oriel Jutty :hhHHHAAAH:@infosec.exchange
        link
        fedilink
        arrow-up
        2
        ·
        8 months ago

        roadmap definition, sprint planning, unit tests, regular independent code reviews, etc. etc. etc. that those of us who “knew what we were doing” mostly looked down on as the waste of time that it was

        You sound insane.

        • pixxelkick@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          8 months ago

          Not really, for humans a lot of this stuff feels like busywork that sorta helps for certain scales of work, but often times managers went WAY too hard on it and you end up with a 2 dev team that spends like 60% of their time in meetings instead of… developing.

          But this changes a lot with AI Agents, because these tools that help reign in developers REALLY help reign in agents, it feels… like a surprising good fit

          And I think the big reason why is you wanna treat AI Agents as junior devs, capable, fast, but very prone to errors and getting sidetracked

          So you put these sorts of steering and guard rails in and it REALLY goes far towards channelling their… enthusiasm in a meaningful direction.

            • pixxelkick@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              8 months ago

              What the fuck are you talking about, thats not what the poster said, you’ve done weird contorting of what they said to arrive at the question you are asking now.

              While some tests make sense, I would say about 99% of tests that I see developers write are indeed a waste of time, a shit tonne of devs effectively are writing code that boils down to

              Assert.That(2, Is.EqualTo(1+1));
              

              Because they mock the shit out of everything and have reduced their code to meaningless piles of fakes and mocks and arent actually testing what matters.

              Do you do code reviews in meetings?

              Honestly often… yes lol

              Do you think testing and reviewing code was a waste of time before “AI”?

              I would say a lot of it is, tbh, not all of it, but a huge amount of time is wasted on this process by humans for humans.

              What the poster was getting at is a lot of these processes that USED to be INEFFICIENT now make MORE sense in the context of agents… you have vastly taken their point out of context.

    • Bane_Killgrind@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 months ago

      Dude this boils down to “moving a hundred people is simple, I am a trained pilot and I used this 747 to move them”

      Like great, you have the thousands of hours of training time required to understand a machine of that complexity and produce results.

      Joe dirt has 8000 hours in his puddle jumper, and that’s the majority of the people these 747s are being foisted upon. They know how to fly, and they provide that service reliably.

      Telling them to move 5 people with a machine they don’t need the volume or distance of, is irresponsible.