Technology

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.

you forgot to wrap access in a _get function

I swear they have to wrapper everything