Remix clone Hacker News

new | show | ask | jobs Github

▲

inejge 2 days ago

My definition, FWIW.

AI-friendly: you can use the LLMs however you wish, but you must thoroughly understand every part of submitted code.

Slop-friendly: understanding anything is optional.

▲

ChocolateGod 2 days ago | parent [-]

I also agree with that definition. But for example if I get an LLM to generate 95% of a program, but I understand and have read every line of code, is it still slop?

Some would say yes unfortunately.

	▲	palata 2 days ago \| parent \| next [-]
		Not the OP, but I wanted to share my 2 cents: As an open source maintainer, when someone opens a PR, I don't know who they are. But I don't really care. I care about the PR: is it a "good" PR (there are multiple dimensions: is it understandable, does it add maintainable code, was it tested, etc) or not? I think "AI-friendly" says "I don't care if it's written with an AI or not: I want good quality PRs". I would think that "slop-friendly" is the kind of projects where the maintainers don't read the code. Maybe they try the feature (maybe not even?). I think the Omarchy guy was explaining somewhere that he does not read the code anymore, he just lets his AI write Rust. This is slop-friendly IMO. If you are not AI-friendly, it means that you refuse to accept a good PR even if you cannot tell that an AI was involved. The mere fact that an AI was involved disqualifies the PR.
	▲	shwaj a day ago \| parent \| prev [-]
		Are you one-shotting then reading/understanding? Then probably slop. Are you iterating to help you understand, prompting to rename/restructure/document until you would have been able to easily understand without AI? Then probably not slop.