As they say, just send me the prompt instead, at least that's more useful.

For anything but the most trivial change, a prompt is not enough though. There's a long iterative process of generating the right code, reviewing it, testing it, experimenting with UX or design for maintainability, fixing bugs... even a predominantly AI-generated PR can capture a lot of value. But apparently trying to distinguish those from the 'one-shot' vibe coded PRs is too much work for the Ladybird team.

	▲	jeltz 2 hours ago \| parent \| next [-]
		> But apparently trying to distinguish those from the 'one-shot' vibe coded PRs is too much work for the Ladybird team. Yes, that is exactly what this announcement is about. That it was too much work for them to tell those two apart.
	▲	m4rtink 4 hours ago \| parent \| prev \| next [-]
		Migh as well just write the thing out yourself - you will learn something by doin that and it will be easier next time. :)
	▲	jeremyjh 4 hours ago \| parent \| prev [-]
		> But apparently trying to distinguish those from the 'one-shot' vibe coded PRs is too much work That is exactly the issue. Projects that are end-user applications - as opposed to libraries or development tools - probably see far more slop than actual work like you've described. The yields are too low for it to make any sense to try to figure out which is which, their time is better spent doing the work.