• ☂️-@lemmy.ml
    link
    fedilink
    arrow-up
    36
    arrow-down
    1
    ·
    edit-2
    7 days ago

    actually, be exactly like bill. boss wants slop, boss gets slop.

    boss wants incomprehensible buggy code? that’s right, boss gets incomprehensible buggy code.

    • dream_weasel@sh.itjust.works
      link
      fedilink
      arrow-up
      6
      ·
      6 days ago

      Be sure to ask Claude to remove all comments, tests, and dry runs, then ask if there’s a good way you can make the code more complicated without increasing runtime more than 40%.

    • psud@aussie.zone
      link
      fedilink
      English
      arrow-up
      6
      ·
      6 days ago

      Sorry, you were hired as a prompt engineer, your prompt wasn’t good enough to make perfect code, so you are fired

      • Shanmugha@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        6 days ago

        Nah. A bunch of llm code review agents say that produced code is of high quality, fire anyone who said it would have taken for them to implement same functionality more time than I have spent

  • el_abuelo@programming.dev
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    6 days ago

    I know I’m gonna get flamed for this, but here goes.

    I have vibe coded a system at work that has enabled me to deliver value in a fraction of the time I expected. My verification steps have been around whether it does the things I told it I wanted it to do. I’m not maintaining the syntax and I’m not expecting anyone else to. Ever.

    That said, our teams that deliver products that touch customer data or financial records…they shouldnt (and dont) engineer this way. The tech isnt there (yet).

    Let the flaming commence.

    • MonkeMischief@lemmy.today
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      6 days ago

      “…enabled me to deliver value in a fraction of the time I expected.”

      I don’t wanna flame you for it.

      This is kinda where I see vibe coding taking off the most: The same phenomenon as using LLMs to summarize and reply to pithy business emails.

      Business gets so unbearably businessy, people are using machines to bypass the inherently un-human “professionalism performance” for them.

      It might not be work anybody can claim to be proud of, but right now success for the professional-managerial class runs on looking busy and circling back to synergizing the workflow with best practices for optimal returns regarding key performance metrics 🤢 or whatnot.

      I don’t blame people for it, in a work context. Looking impressive with AI tools is now a survival tactic when working under normies holding the purse strings and investing stupid amounts of money into the bubble. They’ve forced people to be part of a circular, self-reinforcing imaginary reality they’re profiting from.

      So, I don’t wanna flame you. I just hope you’re doing something fundamentally human to keep your soul alive on the side, at least. Something you as a unique human being on this earth can be proud of. <3

      • el_abuelo@programming.dev
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        5 days ago

        Honestly im proud of the problems I’m able to solve today now that I can use AI to do it so quickly.

        Even when I stop and manually check all the work the AI has done, it’s still much faster and I’m having to rely on my knowledge and experience to do so. When I’m vibe coding I’m relying on that same knowledge and experience to architect the solution rather than deliver it.

        Ive seen the other side- the colleagues who all of a sudden think theyre engineers and are unknowingly exposing critical commercial data to our competitors. That side is scary…and gives me hope that my role while changing, is far from dead.

        Also I have hobbies - i only work to pay for them. If “the man” wants to pay me to spend tokens…fine by me. I’ll be here to clean it up if it all goes wrong.

        • MonkeMischief@lemmy.today
          link
          fedilink
          arrow-up
          1
          ·
          4 days ago

          All good, and I respect your perspective!

          I know you were like “flame me!” Lol, But hope I wasn’t sounding too judgy. I think it’s hard not to have strong opinions on the topic either way these days. (And I’m already prone to soapboxing haha.)

          Wishing you the best out there. :)

    • Shanmugha@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      6 days ago

      He better not have his spine poked by anything sharp :)

      (in cade I failed at it: reference to Midra)

    • JackbyDev@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      6 days ago

      I once heard someone describe legacy systems as systems without test coverage. I think it’s not the best description, but it’s certainly an interesting perspective.

      It’s part of why it bothers me when folks say they use LLMs to make unit tests. If anything, you should be writing tests by hands to get a solid specification then let the AI make the code. Of course this is a false dichotomy, but I’m just saying if you have to choose between those two options in some weird hypothetical bizarro world.

      • Shanmugha@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        6 days ago

        Not the best description doesn’t cut it, it’s just false description. I can easily write a system with 100% test coverage, bugged as hell and containing so many weird abstraction tricks that it takes a significant effort to figure out even what is happening in the simplest scenario. And yes, part of that hundred percent coverage is going to be llm style: test that something does what you already know it does

  • Thetechloop@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    6 days ago

    AI is corpo_slob theft. AI is used to kill kids. AI is a exponential decay feedback loop deskilling method brought to by the capitalist class. It will be used to lower wages. It will create security traps where the corpos can gain… ohhh the drama!!! We need regulation META cries…The lady doth protest too much, methinks, dolla dolla bills ya’ll. It will be used to spy on you and take away your free speech. It is a Poisonous cup of pee. We need more than cheese buger farts and violence. I want to live in a real culture not the techno bro hoedown. After the magic trick, they will pull the rug and you will be left with nothing, without a job. Lower the standards, corner the domestic market, lose the war and claim victory… seems fimilar too me. We are past the point of regulation. Wait til you see the effects of digital ID. They got black sites in the USA were the keep kids in cages… the tech bro and his slave trackers, thats how they get you. Bugs everywhere sold to you as tools and as toys. Language is Language and it changes over time. Empires are built on the ashes of others. Innovation and creation is communication and cooperation. The kings love to pick their fruit of the peasants labor as the knights protect the castles walls. We are entering stagflation and corpotechbro fuedalism. Slop be ass far ass the eye can see. The war in ukraine and the genocide in gaza are connected. The iceburg not fully revealed… the capitalist class is a trashy family… but they stick together and run their games. Look up 7 mountain mandate… now thats some Manchurian candidate

  • 🌞 Alexander Daychilde 🌞@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    2
    ·
    7 days ago

    Woever made this image should learn the difference between line spacing and paragraph spacing…

    This is an example
    of line spacing which
    clearly shows it’s together

    And now this is a new
    bit that is separate from
    the above bit

    Readability is important.

  • chunes@lemmy.world
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    6 days ago

    A lot of the arguments people use against vibe coding sounds a lot like “You shouldn’t use a high-level programming language unless you understand the assembly it compiles to.”

    • pinball_wizard@lemmy.zip
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      6 days ago

      Yes. It’s the same thing, except when I joined the market knowing fuck all about computers, while coding with my cute little BASIC commands; there wasn’t some tech bro asshole telling all the C programmers that their skills would no longer be required. Or at least he (implicated in Epstein files billionaire, Bill Gates) wasn’t saying it quite so loudly (as accused rapist billionaire Sam Altman).

      Incidentally, I still work with that same C programmer, I’m still learning from them, but have since taught them a trick or two; and we both now charge sinful amounts of money for our time.

    • mabeledo@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      5 days ago

      Except for the bit where LLM behaviors aren’t deterministic, but those of most compilers in most situations are.

      And before anyone says that LLVM in version X produced wildly different assembly from version Y, it is not remotely comparable to what LLMs do, not even close.

  • tiredofsametab@fedia.io
    link
    fedilink
    arrow-up
    4
    ·
    7 days ago

    I recently got moved to another team after my company restructured. Several repos have zero documentation. Most of those don’t even have comments on the functions. LinkXxxx(some args) like Xxxx to /what?!/ It’s also an over-engineered mess with multiple layers of abstraction. I can’t wait to finish figuring out what everything does and re-write (and document it) like a sane person. This code presumably had no AI involvement which I’d argue is even worse since real humans made these shit decisions. Don’t get me starting on their testing (and mostly lack thereof)…

    Worker suggested using AI to write some documentation. Another coworker did. I immediately spotted a bunch of hallucinated shit. Good times. I want to know in my head what a thing does, how it works, and how it fits into the architecture. I can’t do that if an AI is just deciding stuff; it’s like a quiz back in school where I would memorize shit for about one week before 99% of it left my brain forever.

    • psud@aussie.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 days ago

      Sometimes documentation doesn’t help. My workplace used to be waterfall and we still have systems analysts producing documentation

      One piece of work came to my team as “this calculation fails in this case and we can’t tell why”

      Looking at it there were two updates in the documentation showing updates ten years ago the first fixing that corner case with the second fixing a side effect of the fix

      Why didn’t it work? It was never built, or perhaps built but never merged

      On the good side we have an excellent plan for how to fix that corner case, on the bad side we aren’t funded to do that amount of work so we have to half arse a solution

      • tiredofsametab@fedia.io
        link
        fedilink
        arrow-up
        1
        ·
        6 days ago

        The documentation I mean here should be in the repo and checked as a part of the PR process. I don’t mean it should be a manual, I just mean a readme should at least describe what the service does (it has such a generic name in my case that it’s not self-evident and is so broad in scope I don’t know what happened). The functions also have terrible naming and no comments to describe what they do. So, as a guy just coming into this team after re-org with no idea what all this stuff does, I was completely lost. They also changed which services which teams owned, further making it difficult to get knowledge.

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    7 days ago

    The code is the comment anyway. The only thing you should comment is things that are way the hell out in left field about why that bit of code exists when it shouldn’t.

  • chicken@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    7 days ago

    I hate most of the companies paying people to write code though, isn’t it a good thing if their code is shit that no one can understand and doomed to collapse under its own weight?