4 ms·
leave a feedback folks:|
by samsep10l 10mo ago
leave a feedback folks:|
- vibesareoff 10mo ago>Use it. Fork it. Improve it. These———LLM———slop———READMEs———make———me———vomit.
- _zoltan_ 10mo agoGet used to it. Nobody will write readmes by hand. I've always hated it and now I'll just let the LLM write it.
- nurettin 10mo agoIt used to be "don't try to outsmart the compiler", I'm waiting for the time people start saying the same thing about LLMs.
- rvz 10mo ago"you're absolutely right!"
- thinkingemote 10mo agoIt's certainly a sign of something. Not positive at best neutral. As you say it's at best an indication that the author doesn't like writing. Could it be an indication that the author didn't write the actual code? Is it a sign that the author doesn't really care that much about their project and furthermore could that be a sign that the project is also be be valued by us as much as the author? Maybe the code quality and documentation is less important than the utility. After all many of us don't like writing tests for code! Perhaps but perhaps we just need to get used to these signs too and get over it.
- samsep10l 9mo ago[flagged]
- latexr 10mo agoThis argument is getting old. Just because you don’t like something, it doesn’t mean everyone agrees and will take the same shortcuts you do. Fortunately not everyone in the world has the same disregard for their own work, and many of us understand the signal it sends when you’re unwilling to even write your own instructions. If you want your READMEs sloppily written by LLMs, that’s your prerogative. Just like it’s the prerogative of everyone visiting your repo and bumping into a slop README to decide if they want to even give your tool a second look before abandoning it. Slop READMEs suggest slop code. Soon everyone who’ll even look at your code are other sloppers and (if it ever gets popular) malicious actors who’ll exploit it in an afternoon because no users understand anything the code does.
- KeplerBoy 10mo agoThen get some freaking taste in READMEs. We can guide the LLMs to better results.
- latexr 10mo agoThe emoji everywhere is what does it for me. Emoji on every title. Emoji on every item of a list. The same ones over and over. So much visual noise. They’re used like a deficient visual crutch.
- mr_mitm 10mo agoI always tell my LLMs: "Try not to sound like an LLM. And no emojis!" Works alright.
- shaky-carrousel 10mo agoMost boring part of developing is writing docs. I see it as boilerplate. If you don't like it, you're free to open a PR.
- vibesareoff 10mo agoThe whole repo is fucking boilerplate.
- samsep10l 9mo ago[flagged]
- brrrrrm 10mo agolooks cool! one bit of feedback: make your demo gif get to the point faster. either practice typing a bit quicker or speed it up 2x for the typing section
- cfcfcf 10mo agoPerhaps consider a public domain film for the demo? https://en.wikipedia.org/wiki/List_of_films_in_the_public_domain_in_the_United_States https://en.wikipedia.org/wiki/List_of_films_in_the_public_do...
- shlip 10mo agoGreat tool I would have loved back when I watched movies :) Could the same be done for music ?
- g947o 10mo agoMight want to add a disclaimer/warning and/or add additional confirmation/wording before downloading. You don't want your user to go to jail because of a mistake that could be avoided: https://news.ycombinator.com/item?id=46364645 https://news.ycombinator.com/item?id=46364645