"Most of the code gets discarded." If you don't mind sharing, what's your signal-to-token ratio?

How do you propose we measure signal? Lines of code is renowned for being a very bad measure of anything, and I really can't come up with anything better.

▲

politician 4 hours ago | parent [-]

The OP said that they kept what they liked and discarded the rest. I think that's a reasonable definition for signal; so, the signal-to-token ratio would be a simple ratio of (tokens committed)/(tokens purchased). You could argue that any tokens spent exploring options or refining things could be signal and I would agree, but that's harder to measure after the fact. We could give them a flat 10x multiplier to capture this part if you want.

▲

mirekrusin 2 hours ago | parent [-]

I'm going to call it out as bullshit, you can't dig out "what you like" from "hundreds agents running all the time".

	▲	_pdp_ 2 hours ago \| parent [-]
		One of our projects has 1.2K open pull requests. https://i.postimg.cc/Jnfk9b8g/Xnapper-2026-02-28-22-25-42.pn... We probably accept 1-2 per day. I personally discard code for the tiniest of reasons. If something feels off moments after I open the PR, it gets deleted. The reason we still have 1.2K open PRs is because we can't review all of them in time. The most likely solution is to delete all of them after a month or two. By that time the open PRs on this project alone will be at least 10-20 more.