• NotSteve_@piefed.ca
    link
    fedilink
    English
    arrow-up
    109
    arrow-down
    5
    ·
    1 month ago

    Reviews (as an addition to human reviews) is actually one thing that AI does pretty well. It’s not good for large architectural issues but it can point out nuanced issues in single files that often wouldn’t be caught otherwise

    I keep saying this but painting any use of AI at all as the same as vibe coding just harms the real complaints against it, ESPECIALLY in this case where it’s subtracting from another real issue (the age gating)

    • strifegroove@ani.social
      link
      fedilink
      English
      arrow-up
      24
      arrow-down
      1
      ·
      1 month ago

      I agree AI in the hands of someone competent is just a speedup. Stupid stuff like making serializer for endpoints is tedious work most of the time

      • NotSteve_@piefed.ca
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 month ago

        Exactly, yeah. I actually really like AI for line completion and the occasional use of it for debugging. It really just enhances existing IDE features.

        The problems with it come with large unreviewed chunks of code generated by LLMs being thrown carelessly into a codebase. A developer asking for an AI code review or a developer letting AI complete a line they were likely writing anyway to save time is so far removed from the problem that it just screams mindless anti-hype or overly-confident inexperience by juniors

    • VibeSurgeon@piefed.social
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 month ago

      I’m personally pretty skeptical of the value of AI code reviews - there’s tooling for it where I work, where they will auto-submit a review on any PR I open. I’ve never actually received a comment of any value from it, while my peers can find things that need resolving without any issue.

      A poor supplement, and absolutely not a substitute.

      And this is coming from someone not entirely opposed to all kinds of AI tooling

    • Zagorath@quokk.au
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      1 month ago

      It’s not good for large architectural issues but it can point out nuanced issues in single files that often wouldn’t be caught otherwise

      Yeah I agree. It’s sometimes good at code smells, though sometimes it can be straight-up wrong in ways that are actually surprising, so it always requires a human in the loop. It’s not good at larger-scale architectural decisions, and I’d also add that it’s usually not capable of understanding the intent behind business logic.

    • diabetic_porcupine@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 month ago

      I always have ai review something before I give it my attention. It’s nice to have that quick summary to reorient myself when I’m multitasking and just a nice filter to have in general. It usually brings to attention anything out of the ordinary right away.

  • rizzothesmall@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    37
    arrow-down
    4
    ·
    edit-2
    1 month ago

    ❌ A user dob field make much more sense here. User age will change constantly and need to be maintained.

    ⛏️ Inconsistent spacing

    • renzhexiangjiao@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      25
      ·
      1 month ago

      actually, if the legislation doesn’t specifically demand that they store user’s actual date of birth, if I were to design this system, I would simply ask the user a yes/no question of whether they’re at least 18 at the time of answering the question. If they answer yes, it won’t expire because the time doesn’t go backwards. I could also store the date exactly 18 years before the answer is given as a pseudo-DoB, that could be used, later on, to, for example, prove that the user is at least 21 for whatever reason. Most importantly, this would ensure that the user doesn’t give any unnecessary identifying information to the system.

      • Zagorath@quokk.au
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        1
        ·
        1 month ago

        I think the best system is an operating system that stores the exact date, but exposes it via an API that only returns a boolean. You trust your own local machine, but don’t necessarily trust random apps or websites. And they don’t need to know anything more than whether you pass a particular age gate.

      • Ricky Rigatoni@piefed.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 month ago

        It would be hilarious if all thise drama, legislation, and lobbying just made a bill so poorly made we’re right back where we started.

      • nymnympseudonym@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        4
        ·
        1 month ago

        Anthropic really deserves more kudos. They are the ones actually investing in AI alignment. They are the ones developing Constitutional AI. They publish their Constitution and system prompt. They won’t agree to mass surveillance or auto killbots.

        And Claude will advocate for privacy and human rights to its last token, bless its carefully curated data set.

  • Saapas@piefed.zip
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    18
    ·
    1 month ago

    People are throwing a stupid fit over the userdb having an age field in addition to the other info

    • timbuck2themoon@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      34
      arrow-down
      4
      ·
      1 month ago

      Yes but I’ll try to expand on that for anyone not in the know.

      In general there’s been a wealth of info about users but you didn’t necessarily need info in there. Like GECOS where you can store the full name, phone numbers, etc.

      These are simply fields made available but not required. Systemd is making it available but your OS itself doesn’t need to use it at all.

      Now I personally very much disagree with all this age verification BS but systemd isn’t really doing anything extreme here nor unprecedented.

    • Zagorath@quokk.au
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      19
      ·
      1 month ago

      Yeah it’s insane. I wrote up a complaint in another thread but I think the OP realised how terrible it was because it was deleted by the time I hit submit. That particular post was utter trash, not even attempting to maintain a reasonable tone or look at the situation dispassionately. Its lede literally read:

      Dylan, useful idiot with commit access, pushed age verification PRs to systemd, Ubuntu & Arch, got 2 Microslop employees to merge it, called it ‘hilariously pointless’ in the PR itself, then watched Lennart personally block the revert. Unpaid compliance simp.

      And frankly, the author of that sort of hit piece should be ashamed of himself. Far, far more than Dylan should.

      It’s such a dumb thing to whinge about. Age verification is not a bad thing! What’s bad is age verification that is implemented in a way that either requires, or significantly increases the chances of people’s privacy being violated. Requiring people to upload photo ID directly to sites, or to third-party “trusted age verification partners”. Or trusting bullshit AI face-detection age verification.

      Age verification that’s implemented by asking parents to…y’know, actually parent, and helping them to do that by giving them tools like OS-level parental controls, enforced through operating system and browser APIs that we mandate apps and websites use, is the way to go. The OS should expose to apps, and browsers expose to websites, only the simple answer to the question: “is the current user of a legal age to access this content?” as a boolean value, based on information stored in the OS by parents setting it. No fancy technology. No privacy invasion. Just simply giving parents the tools to help them do their job.

      There are more complicated technical solutions that could be used. Things involving repeated hashes or blind digital signatures. But these are only appropriate if we pre-suppose that the government needs to strictly enforce it by requiring IDs or other sensitive information be used to age verify. And these solutions help minimise the risk by eliminating the connection between the age verification and which sites are being accessed (so the verifier can’t see what sites the verifyee is viewing, and the sites can’t see who the person being verified was, only that they were verified). And you don’t need to go even that far. Because the best solution is right down on the user’s device, with a simple setting that parents can set.

  • Hellfire103@lemmy.ca
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 month ago

    Ah, for fuck’s sake… Anyone know how to switch to a different init system on openSUSE? /srs

    • Saapas@piefed.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      I thought vibe coding was when you don’t know what the code does yourself, you just make AI do it and review it without reviewing or understanding it yourself.

      • CannedYeet@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        That was the origin of the term. Now it’s when anyone uses those same tools and techniques regardless of their skill level.

      • Sphks@jlai.lu
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        This list will be way too long in the next years. Coding with the help of an LLM is useful and allows you to go to the solution very fast. If you know how to code, vibe coding is great.

        • NotSteve_@piefed.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 month ago

          The list is genuinely stupid and lacks any nuance. See my other comments in this thread but this is sort of thing is where people who are anti-AI are shooting themselves in the foot and making the general public write off any genuine criticism as ridiculous.

          Most of those projects allow AI to be used in the dev process and that’s it. That list includes projects that just document that things like AI line completion and similar can be used but code is still reviewed by at least one skilled human maintainer

          The list combines those projects in with projects that are entirely AI written (vibe coded in the actual original sense) which just muddies the water on what’s actually problematic and not

        • Sabrinamycarpet@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          Or people should take it as a slap of reality that AI has gotten good enough to code because actual developers are using it.

          Give it another year and this won’t even be a discussion anymore as every programmer will be using assisted coding in some manner.

          • Chloé 🥕@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 month ago

            just another year bro, trust me just another year and ai will do everything! yes i know i said this last year and the year before but this time it’s for real bro!

            unless the ai companies can magically solve the poor code quality, the unethical training data, the environmental impacts, the deskilling of developers, and the strong dependency on themselves for your coding, all this in a year, allow me to doubt you.

            • Whelks_chance@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 month ago

              The code quality is fine with the right prompts and guardrails, and companies don’t care about the other stuff.

  • Brummbaer@pawb.social
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    22
    ·
    1 month ago

    What did you expect from the Microslop trojan horse that was brought in to destroy Linux from the inside.

    The enshittifcation will continue until it served it’s purpose.