@bekkaboo@girlcock.club Linux itself is heavily using AI models. Therefore, every Linux distribution moving to recent kernel versions is heavily built on top of using AI models. Creating a Linux distribution not heavily using it would require a hard fork of the Linux kernel and many other projects.
It's unclear what would be accomplished by banning AI for a tiny portion of the code while continuing to use Linux, AOSP, Chromium and hundreds of other projects heavily using it. We'd still be benefiting from it.
GrapheneOS is currently defending its use of AI coding tools on Mastodon against complaints by various accounts claiming to be users.
We do not understand where you’re coming from or why you’re so incredibly angry with us. It’s not justified and does not make sense.
A bit unrelated, but I wonder if I’m the only one left that is:
Using small, open-weight models
Asking it to only write small snippets that I can easily go through, check and understand.
Copying pasting from good old web frontends instead of integrating it into my editor or whatever else people do with agents nowadays.
I feel like when we’re talking about AI this sort of usage gets lumped into the same pile as agentic vibe coding and it’s not helpful for discussion. Surely most people wouldn’t find this problematic?
I prefer it less for the writing part (unless big refactors that aren’t actually complex) and more for analysis. If you got a couple million lines of code upstream that you depend on heavily (ERP modules) then it’s nice to fire off a prompt and come back to “you got weird behavior x because upstream changed y, here’s the exact file and lines and how it flows there”
My company is currently pushing “loop engineering” on us… They are in love with Claude and keeps referring to it as “him”. Very proudly announce that “I set ut a loop, and he closed 40 PRs while I slept!” (without review, of course). Based on vibe written tickets as well, which contains many hallucinations.
The poor QA department (2 people) is now trying to figure out how to test all the slop.
A bit unrelated, but I wonder if I’m the only one left that is:
I feel like when we’re talking about AI this sort of usage gets lumped into the same pile as agentic vibe coding and it’s not helpful for discussion. Surely most people wouldn’t find this problematic?
I prefer it less for the writing part (unless big refactors that aren’t actually complex) and more for analysis. If you got a couple million lines of code upstream that you depend on heavily (ERP modules) then it’s nice to fire off a prompt and come back to “you got weird behavior x because upstream changed y, here’s the exact file and lines and how it flows there”
Probably.
My company is currently pushing “loop engineering” on us… They are in love with Claude and keeps referring to it as “him”. Very proudly announce that “I set ut a loop, and he closed 40 PRs while I slept!” (without review, of course). Based on vibe written tickets as well, which contains many hallucinations.
The poor QA department (2 people) is now trying to figure out how to test all the slop.
We usually say “the other guy”, or sometimes we say “I & AI” (a poor twst on a Rastafarian saying)