It's surprisingly difficult, and the "obvious" techniques (just do embeddings) don't really work. I wrote about it and did benchmarks here: https://joecooper.me/blog/redundancy/
Thank you for actually testing and measuring an implementation & hypothesis. I appreciate the leads for evaluating my own similarity problems and efficacy.
Because there's no money in trying to filter out noise that costs next to nothing to generate. It's like asking why no startup is trying to bring forum moderation to the masses.
I recently published this project that aim to help me with a similar issue that I was facing. A lot of PR and commits that I wanted to further reviiew outside of Github to understand better the changes: https://github.com/lertsoft/DiffLearn
The author of this Tweet has been making waves by talking about using AI to write code without reviewing it. He wasn’t actually reading and reviewing all of that code himself.
As for the pace: His project has become extremely popular and got him a very nice position at OpenAI just today.
The reviews must be heavily AI assisted in order to get that sort of volume in.
Either way, it doesn't surprise me that this number is so high. Productivity chasing is the name of the game for AI, regardless of how sustainable or helpful this extra work done actually is
No one else has done it and code is easier than ever to create. This tool needs to be built by the person closest to the problem.
Ask your agent for ways to do this using code, not more AI.
It might propose - and build! - an embeddings based system and scraper for your issues & PRs. Using that will burn zero tokens and you can iterate on it as you think of improvements.
I mean you can just do this with claude code or opencode. I suggest opencode and gemini pro since it has a nice big context window. If you are trying to do something like this on the website version of the models just forget it, stop using those, they are like toys compared to the CLI tools.
Step 1: have it sum up every issue and pr in like 100 words. You can have it do it using subagents working on subsets of the tickets so it doesn't take forever.
Step 1a: concatenate all the summary files to one big file.
Step 2: have it check pairs that seem duplicate from the summary. You may have to force it to read the entire file, for whatever reason models are trained to try to avoid just reading stuff into their context and will try grep and writing scripts and whatever else.
Step 3: repeat the above until it stops finding dupes.
I think this will probably take about 4 hours? 2 hours to get the process working and 2 hours of looping it.
If you don't think the above will work well please just move along, don't bother arguing with me because I've done tasks like this over and over and it works great.
Ways to get better results in general:
- Start by having it write a script to dump all the relevant information you will need up front. It's much faster at reading files than trying to do mcp calls. It's also less likely to pretend to read files and just assume it didn't find anything. (happens more than you think)
- Break the problem down into clear steps for the model, don't just give it a vague project. Just paste the steps above and it should work fine.
- Check what it is doing. Don't assume that because it says it read a file it actually read it, it will very often read the first 1000 bytes, then not read any of the rest of it, then just assume it read everything. In fact ChatGPT will complain that the input is truncated when it is the one that chose to only read the first part.
I asked Copilot (work) to do this with a sheet and the summary it gave each time was so generic I couldn't tell one ticket from another. Feeding it tickets individually was fine, but in a spreadsheet it just seemed to forget.
Would be interested to learn how we can get true foreach loops.
thatjoeoverthr|14 days ago
donavanm|13 days ago
CodingJeebus|14 days ago
Because there's no money in trying to filter out noise that costs next to nothing to generate. It's like asking why no startup is trying to bring forum moderation to the masses.
pavel_lishin|14 days ago
Not yet, but when there's so much more noise than signal, it'll become valuable.
ranger_danger|14 days ago
forty|14 days ago
forty|14 days ago
lertsoft|9 days ago
DangitBobby|14 days ago
zahlman|14 days ago
ranger_danger|14 days ago
Why? There's no reason you need to actually handle that many in a day, right? Pace yourself.
Aurornis|14 days ago
As for the pace: His project has become extremely popular and got him a very nice position at OpenAI just today.
slowcache|14 days ago
Either way, it doesn't surprise me that this number is so high. Productivity chasing is the name of the game for AI, regardless of how sustainable or helpful this extra work done actually is
cadamsdotcom|14 days ago
Ask your agent for ways to do this using code, not more AI.
It might propose - and build! - an embeddings based system and scraper for your issues & PRs. Using that will burn zero tokens and you can iterate on it as you think of improvements.
ltbarcly3|14 days ago
Step 1: have it sum up every issue and pr in like 100 words. You can have it do it using subagents working on subsets of the tickets so it doesn't take forever.
Step 1a: concatenate all the summary files to one big file.
Step 2: have it check pairs that seem duplicate from the summary. You may have to force it to read the entire file, for whatever reason models are trained to try to avoid just reading stuff into their context and will try grep and writing scripts and whatever else.
Step 3: repeat the above until it stops finding dupes.
I think this will probably take about 4 hours? 2 hours to get the process working and 2 hours of looping it.
If you don't think the above will work well please just move along, don't bother arguing with me because I've done tasks like this over and over and it works great.
Ways to get better results in general:
- Start by having it write a script to dump all the relevant information you will need up front. It's much faster at reading files than trying to do mcp calls. It's also less likely to pretend to read files and just assume it didn't find anything. (happens more than you think)
- Break the problem down into clear steps for the model, don't just give it a vague project. Just paste the steps above and it should work fine.
- Check what it is doing. Don't assume that because it says it read a file it actually read it, it will very often read the first 1000 bytes, then not read any of the rest of it, then just assume it read everything. In fact ChatGPT will complain that the input is truncated when it is the one that chose to only read the first part.
ferngodfather|14 days ago
Would be interested to learn how we can get true foreach loops.
tayo42|14 days ago
7e|14 days ago
tantalor|14 days ago
akmarinov|14 days ago