Can understand it to be frustrating to see your repo overwhelmed with sloppy PR, and having agents putting out threats is obviously wrong.
However you are essentially offered free tokens. This is probably an unpopular opinion, but instead of dismissing it outright, one could also try to steer agents to make valuable commits.
Personally I put an automation friendly CONTRIBUTING.md on my new repo. Still has to be tested in practice though. Giving it a 50% chance may regret this. Time will tell.
It is absolutely possible to enjoy both- I have used LLMs to generate code for ideas about alternate paths to take when I write my code- but prompt generation is not coding, and there are WAY too many people who claim to be coding when they have in fact done nothing of the sort.
> a far higher intensity
I'm not sure what this is supposed to mean. The code that I've gotten is riddled with mistakes and fabrications. If I were to use it directly, it would significantly slow my pace. Likewise, when I use LLMs to offer alternative methods to accomplish something, I have to take the time to sit down and understand what they're proposing, how to actually make it work, and whether that route(s) would be better than my original idea. That is a significant speed reduction.
The only way I can imagine LLMs resulting in "far higher intensity" is if I was just yolo'ing the code into my program, and then doing frantic integration, correction, and bugfix work afterwards.
Sure, that's "higher intensity", but that's just working harder and not smarter.
Author here. Thanks for asking. One key objective is not to be yet another linksite, but add utility by providing direct shortcuts to code, docs, api references etc. next to the main link.
> One key objective is not to be yet another linksite, but add utility by providing direct shortcuts to code, docs, api references etc. next to the main link.
Is this a need people have? I would use letsbuild.ai to discover projects and check their homepage/documentation, but once I know a given project I know where to find its docs (or search for "<project> docs" on Google).
don't underestimate the UX improvments from tiny friction removal features. It can become the difference between a site no one usess to a site everyone loves
> don't underestimate the UX improvments from tiny friction removal features. It can become the difference between a site no one usess to a site everyone loves
Which UX improvements are you thinking of exactly? This is a website I would personally not use because all I see is a list of links without context nor explanation about which tool is better than another for which task.
However you are essentially offered free tokens. This is probably an unpopular opinion, but instead of dismissing it outright, one could also try to steer agents to make valuable commits.
Personally I put an automation friendly CONTRIBUTING.md on my new repo. Still has to be tested in practice though. Giving it a 50% chance may regret this. Time will tell.