0natcer

the argument is not that AI PRs are inherently not valuable. but if you have to spend a lot of time triaging them because of slop AI PRs it is just draining and inefficient.

You can enroll here: https://github.com/anthropics/oss-scanner

when they launched this in beta they asked what they should improve. most of the comments asked for making the agent sections removable. guess what they didn't change.

If you don’t know what happened how would you be able to tell if the changes are addressing the problem? If you don’t care about the problem being addressed why jump in a call in the first place?

Five frontier LLMs 100% agree that the title is misleading.

for anyone interested <selfpromo>i made a video about the project where this the lambo part is featured in https://youtu.be/EGOkjmyfL6E?si=gn9LQ87gBRs9q9tL&t=60 </selfpromo>

Laravel dev here too

i just wanna add here on a serious note that i also see a use cases for "server actions", but i do not primarily write next.js or react so i didn't have an opportunity to try them out yet.

I think it's important to know what you would use them for. I don't think core business logic should be there, but I see why you would use them for f.e. signing something that would require a secret you don't want to have on the client side.

I do however think that it's not a good idea to show the inline code example in a presentation. fortunately none of those examples exist in the documentation. having a seperate file with server actions that can be imported is a good way to handle it i think.

Wish I counld just click on the "Size", "Files", "Added", "SE" and "PE" to order them...

This looks pretty awesome. Hope I can try it out in a project some time soon...