Poliorcetics

71 Followers
113 Following
837 Posts
Rustacean 🦀, devourer of fruits 🍎. I love cats too, the one in the photo is the scrungiest I ever met !
🐙 Githubhttps://github.com/poliorcetics
As the number of LLM-generated patches in my inbox increases, I am starting to experience the sort of maintainer stress that has long been predicted. But there's another aspect of this that has recently crossed my mind.

Just over a week ago, a new personality showed up with a whole pile of machine-generated patches claiming to fill in our memory-management documentation. A few reviewers had some sharp questions, the response to which has been ... silence. This person doesn't seem to have cared enough about that work to make an effort to get past the initial resistance.

Once upon a time, somebody who had produced many pages of MM documentation would be invested enough in that work to make at least a minimal attempt to defend it.

Kernel developers often worry that a patch submitter will not stick around to maintain the code they are trying to push upstream. Part of the gauntlet of getting kernel patches accepted can be seen as a sort of "are you serious?" test.

When somebody submits a big pile of machine-generated code, though, will they be *able* to maintain it? And will they be sufficiently invested in this code, which they didn't write and probably don't understand, to stick around and fix the inevitable problems that will arise? I rather fear not, and that does not bode well for the long-term maintainability of our software.

First they ask for your date of birth,
but later they claim it's not enough.

Then they ask for your full name and location,
but later they claim it's not enough.

Then they ask for a copy of your passport,
but later they claim it's not enough.

Then they ask for your facial scan,
but later they claim it's not enough.

Then they ask for your fingerprints,
but later they claim it's not enough.

Then they ask for your palm scan,
but later they claim it's not enough.

Then they ask for a scan of your iris,
but later they claim it's not enough.

Then they ask for ...

#MassSurveillance #Authoritarianism #AgeVerification #Privacy #Democracy #HumanRights

@ekuber @yosh I know but your example seems to indicate you want a different way to specify it ?
@ekuber @yosh if I write a function taking multiple i32s it should also be possible to write per-arg behavior no ? Not all i32s are created equal, though for the vast majority of functions they likely would share the same so having a default through the type would be a good default

My #Wikipedia request for comment just closed, finally banning #AI content in articles! "The use of LLMs to generate or rewrite article content is prohibited"

Kudos to all who participated in writing the guideline (especially Kowal2701) and the whole WikiProject AI Cleanup team, this was very much a group effort!

https://en.wikipedia.org/wiki/Wikipedia:Writing_articles_with_large_language_models/RfC

Wikipedia:Writing articles with large language models/RfC - Wikipedia

@ariadne ohhh, okay, I missed that the first part was using public and the second private, thanks!
@ariadne having not looked too much into capsudo, I think I get the gist but what is happening in the delegator command line with the two capsudo calls ? (Is the second even a call ?)
@bagder do a recursive task to add a new graph every year 😁