Such a luxury, I am envious!

Our team started using AI, so I switched to a simple method: no comments, and a binary "is this batshit crazy or passable" approval decision rule.

Saving myself time and sanity.

▲

Sharlin 4 hours ago | parent | next [-]

In other words, AI code is owned by nobody.

	▲	randusername 3 hours ago \| parent \| next [-]
		AI code is owned by owners and society is figuring out in real-time if code has some inherent value without humans that understand it. I'll be really interested to follow what comes out of the Bun team.
	▲	kibwen 3 hours ago \| parent \| prev \| next [-]
		It's not innacurate to say that AI code becomes legacy code the instant it's merged.
	▲	nijave 2 hours ago \| parent \| prev [-]
		Tragedy of the commons

▲

acedTrex 4 hours ago | parent | prev [-]

Yep, without a decent team culture this is what LLMs force, the slop deluge is just overwhelming without leadership asserting "no, stop"

Ultimately you just let bugs through because the alternative is spend an inordinate amount of time communicating with someones claude through PR comments about what the shape should be.

Career was fun while it lasted. I suppose its a blessing a to get to do a job that you enjoyed for as many years as I did.

	▲	morganherlocker an hour ago \| parent [-]
		Disapprove and ask for a call where the author must verbally explain the changes to receive approval? This seems like a solvable problem, and one that already existed in repos with many contributors of varying skill (open source, bigco with lots of interns). Letting bugs through is an even bigger time sink.