LOL. Speak of the devil, some slop coder just opened a massive PR on our codebase with gems like:
func runHandler(h: Handler)
// ^^^^^^ ERROR: runHandler will panic if h is nil
// Severity: High 🚨
Uh... yes? Do you not know how pointers work? That's the point? You want to be able to run runHandler(nil)? That doesn't make any sense. That's clearly a mistake and we should loudly fail.
type OptionsWrapper struct {
Foo bool
otherOpts other.Opts
}
// ^^^^^^ ERROR: OptionsWrapper hides options only available in other.Opts.
// Severity: High 🚨
Uhh... yes? That's the whole point of OptionsWrapper. To hide stuff otherOpts. It's a wrapper.
This type of clanker output is why another slop coder opened a PR on one of our repos, angry because he said Claude said that one of our functions was deceptive. Claude said the description and docstring was misleading and we should change it.
Our function was called RunNoWait() and, hold on, you may be surprised by this, Claude was, what this function does is run something... and then it.... does... NOT wait. wtf. I know. Shocking. Misleading, deceptive name. Claude wrote some big manifesto about why the docs were misleading and rewrote the function to add a wait. 🤣
The dude backed down eventually, but he insisted we add more paragraphs of clarification to the function docs...
If it's anything like Claude on our codebase then:
const id = "foo"
// ^^^^^ WARNING!!!! GO MIGHT NOT BE ABLE TO ALLOCATE THE MEMORY FOR THIS STRING!
// Here's an Enterprise String Implementation to guarantee this assignment works.
// Severity: High 🚨
It's like Tailscale, but Open Source. You can self-host the components, if you want. I just use the cloud offering. I have a domain name that resolves to my server. There's different ways you can do auth. I just hard coded an allow list of IPs. Otherwise, devices in my Netbird network can use the private IP.
The share option within Claude tells a user that "anyone with the link" may view the contents of that link, but does not explicitly state that the link may end up in Google and search results.
It seems like people clicked the "make chat public" button and then shared the link with someone who eventually posted it on a page that got crawled?
Maybe there's two mistakes here: 1: the user made the chat public and 2: Maybe Anthropic didn't have their robots.txt file set correctly?
I mean, it seems like the big mistake here is from the users... they clicked the "make this chat public"... unless I'm missing something?
The searches showed Claude chats for which a user had decided to "share" a link had been saved by search engines like Google, leaving them accessible to the broader public.
So... people created public links, shared them to the public, and got surprised they were public?
The share option within Claude tells a user that "anyone with the link" may view the contents of that link, but does not explicitly state that the link may end up in Google and search results.
Boosters: There's no way to enforce this! This rule shouldn't exist. You can't be 100% sure a project isn't slop. Keep the flood gates open.
Reality: We also can't 100% enforce that people follow the speed limit, but we have speed limit laws. When we catch someone, we can point to the law. The mere existence of the law also acts as a small deterrent.
Same with Codeberg. We can't 100% enforce the ban, but when we catch someone we'll be able to point to the rule and kick em out. And just seeing an "AI not welcome" sign on the wall will deter some amount of people.
Software engineers still have a job to do, AI has just changed it, said Ethan Mollick, an associate professor of management at the University of Pennsylvania’s Wharton School and author of the upcoming book Co-Existence.
“Now it’s not about who can write the most code,”
Who the fuck... when the fuck... it's NEVER been about who writes the most code.
LOL. Speak of the devil, some slop coder just opened a massive PR on our codebase with gems like:
func runHandler(h: Handler) // ^^^^^^ ERROR: runHandler will panic if h is nil // Severity: High 🚨Uh... yes? Do you not know how pointers work? That's the point? You want to be able to run
runHandler(nil)? That doesn't make any sense. That's clearly a mistake and we should loudly fail.type OptionsWrapper struct { Foo bool otherOpts other.Opts } // ^^^^^^ ERROR: OptionsWrapper hides options only available in other.Opts. // Severity: High 🚨Uhh... yes? That's the whole point of OptionsWrapper. To hide stuff otherOpts. It's a wrapper.
This type of clanker output is why another slop coder opened a PR on one of our repos, angry because he said Claude said that one of our functions was deceptive. Claude said the description and docstring was misleading and we should change it.
Our function was called
RunNoWait()and, hold on, you may be surprised by this, Claude was, what this function does is run something... and then it.... does... NOT wait. wtf. I know. Shocking. Misleading, deceptive name. Claude wrote some big manifesto about why the docs were misleading and rewrote the function to add a wait. 🤣The dude backed down eventually, but he insisted we add more paragraphs of clarification to the function docs...
Whatever. Let the slop flow..... I give up.