Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: AISlop, a CLI for catching AI generated code smells

github.com

Post reply on HN
Print view View original

31–40 of 70 posts

Re: Show HN: AISlop, a CLI for catching AI generated code smells

#32

Post by beart »

Retr0id wrote: post #28
Heavykenny wrote: post #24

Earlier quoted context omitted.

haha. I love the name - aislop

Forgot to switch accounts?

OP seems to be an AI account.

> Don't post generated comments or AI-edited comments. HN is for conversation between humans.

Re: Show HN: AISlop, a CLI for catching AI generated code smells

#33

Post by ryandrake »

I think a lot of the telltale signs of AI can be found in the comments. Besides the slop writing style, I've found AI comments to 1. be overly verbose, 2. unnecessarily describe before/after code state (# This function used to do foo, but now it does bar), and 3. reference its own internal "plan" (# This function is part of Stage 3 of the implementation of Use Case X from the requirements doc) WTF is Stage 3? - says code reader 2 years from now. Although I bet you can probably prompt these behaviors away.

Re: Show HN: AISlop, a CLI for catching AI generated code smells

#35

Post by macNchz »

I don’t see if this is one of the covered cases, but one of the more common and nefarious patterns I run into is what you might call "sweeping exceptions under the rug." I think the agent’s motivation to get things running encourages these antipatterns of designing routines that are fault tolerant in a sort of maladaptive way: e.g. catching an error, logging a warning that something didn’t work, and continuing, but with now potentially missing/broken state.

This has bitten me a couple of times, and it’s surprisingly annoying to nudge agents into good/resilient patterns or identify situations that should fail loudly, at least in my experience. The retry mechanisms they come up with on their own are often pretty terrible as well.

I’ll note, though, that I have seen this from human engineers plenty of times, and at least the AI usually adds some logs rather than just totally silently absorbing an exception!

Re: Show HN: AISlop, a CLI for catching AI generated code smells

#37

Post by hootz »

Aurornis wrote: post #14
hootz wrote: post #10

Earlier quoted context omitted.

Yeah, to be honest, it really is a bit weird to incorporate a tool called slop into a corporate CICD flow. Anubis fixed a similar problem by creating a corp-safe version without the anime mascot.

> Anubis fixed a similar problem by creating a corp-safe version without the anime mascot. I wouldn’t say they fixed it. Rather it was an intentional choice to put an anime girl on websites unless you paid for the product.

Fair, I guess that doesn't apply here then, as I don't think the intention of OP is to drive corps away from the main free product.

Re: Show HN: AISlop, a CLI for catching AI generated code smells

#38

Post by add-sub-mul-div »

fishgoesblub wrote: post #31

Apparently I need to check in with a Doctor because code written by myself is seen as AI, and the lazy AI bits aren't. More Human than Human?

Unfortunately, AI detection can never be assumed to be accurate for the same reason the AI itself can never be assumed to be accurate.

(Not that I think you didn't probably already know that.)

Post reply on HN