gokaygurcan

haha i know, right

Yes, we were all 6h old babies at some point. Some of us became great people, some of us became terrorists or worse. Takes some time to see where we end up with. No different for these resources, especially the repositories. If it's an internal tool that's heavily used, then made public with a wiped history, maybe your argument is correct but if it's a never-done-before/new approach to any problem, it needs some time to see the traction and proof.

There's also some form of outcome bias here. You're judging the resource/repository/library/whatever from today's learnings and standards, but it took this amount of time to reach here, maybe do-over multiple times, 100s or 1000s of commits and clearly none of these were there when it was only 6h old.

I appreciate the suggestion but in this case I don't believe the solution to AI problem is using more AI. I personally believe what makes these lists "awesome" is the human element, not some deterministic checks that another agent could run.

I help maintaining one of these awesome lists, awesome-javascript, since 2018. There's been always self-promoting or similar activities, or someone coming up with an idea/forking a repository and doing some small changes, then thinking they're suggesting something groundbreaking. Because of this, we needed to add a few checks over the years to the pull request template, that basically asks if the resource is out there for a while, actively maintained, actively used by people, etc.

Recently, thanks to AI being this cheap and accessible, the amount of shitty PRs quadrupled if not more. And the worst part? Agent doesn't care about the checklist at all and re-writing the PR body with bunch of nonsense that we maintainers need to read, understand, and evaluate. I started keeping the score for the most shittiest PR based on how soon after the first commit made they open the PR. It was 11h, then 10h, and now it is 6h. How on earth a 6h old repository with zero user is considered "awesome" I don't know, but people should stop prompting their agents to create 10s of these PRs every day.

Yes, there's always an alternative: stop maintaining these lists. I don't think it's a viable option either. Sometimes you start using a new piece of tech and want to have access to somewhat curated list of resources that might speed up your understanding. There's still a bit of value to keep them alive and it's dying out bit by bit (literally) every time someone mass-creates these spammy PRs.

Thanks for reading my unsolicited rant.

> see a new programing language > look inside > it's rust

asking out of my own ignorance, what's so hard with rust that you cannot convince people and contribute to that directly instead of going on your way? i remember so few of these projects survived over the years. do you think it'll really become something other than your pet project?

Nice concept. 6 people, it was fun, 18 people, not so much. Can't imagine a few hundreds, prolly pure chaos.

Maybe different people seeing different pieces from different sides would help with the chaos, idk.

Do you have a price range in mind?

I frequently use them both. The main reason why I can't leave Charles is the lack of session grouping in Proxyman. Seeing a huge list of irrelevant items is annoying after some point. In Charles, I can save that session with a name and move on to something else. It's almost impossible to leave one for the other at this point for me.

This goes without saying, but huge thanks to the both developers for making these available.

Great initiative.

Love this app. You don't have to be a professional birdwatcher (if that's a profession) to use it. Just open it, and start listening. It's really fun to see what kind of variety of birds around you.

I've spent so many hours of my life for this game.

Also shared it with many people and made them go crazy. I believe I still have 5 or 6 copies in my Steam inventory. Just in case.

Same for V, SMB, Braid and so many others. Sometimes, all you need is a little inspiration and crappy graphics.

Before it was moved to GitHub Actions, we had a multiple-step deployment flow created in Node-Red, I believe you can achieve more or less the same thing with n8n. Never tried tho, it wasn't necessary anyway. If I really really simplify it's like, checkout, run some tests, deploy to a preview env, run some more tests, report back to slack.

On a personal level, I use it to automate booking a tennis court. It logs in, selects the date and time (pre-defined), adds a partner/opponent, books the court, pings a service that generates a calendar entry. If I decide to cancel the booking, it again pings the service and removes the calendar entry. I needed to bend some "nodes" to do what I need within the same workflow (such as create event runs once a day but update event runs in every 10 minutes).

In the past, I also used it to detect service interruptions with my ISP. I don't use that ISP anymore, so this workflow is redundant, but it was checking an API and if there's an entry, sending it as a push notification (via ntfy) to my phone.

This deserves a medal, come on!

I guess at this point if you want to do something new/modern, go for 4- or 8-star rating rather than 5- or 10-star rating. It'll force people to choose something other than middle. I hate to find 3/5 book which really deserves 2/5 but people didn't want to leave somewhat negative feedback.

Maybe out of context, but the real value of Goodreads is the sheer number of content (books, reviews, lists, users, etc). If something _works_ there's not always a reason to break it and/or update it just for the sake of updating. Look at hardcore Salesforce tools, they look like they're from 90s, but they work perfectly fine. If that's your only motivation, it's impossible to win me over as a user.

Side-note: create a new book list and call it DNF, add the books that you didn't finish to that list and get it done with.