☆ Yσɠƚԋσʂ ☆

  • 610 Posts
  • 640 Comments
Joined 7 years ago
cake
Cake day: January 18th, 2020

help-circle






  • First of all, that’s obviously false. Second of all, go look at unemployment rates in USSR. You literally have no clue regarding the subject you’re attempting to debate here. However, even your whole premise is insane. We shouldn’t strive to do work for the sake of work. Automating toil away so people can spend their lives in a self directed fashion is unarguably a good thing. You’re just arguing for having what David Graeber called bullshit jobs here.






  • Using LLMs to vomit out all of your code into one commit is vibecoding. It’s clearly vibecoding when there weren’t even multiple commits. No trial and error, no refinement, just one giant dump.

    Yeah, I completely agree there. Just like with regular coding, you have to go slowly, implement functionality in small focused chunks, review, and iterate.

    And I’d also wait and see whether the project continues to be maintained before considering it. I just posted it because I thought it was neat, and might be worth watching to see how it develops, not that I’d use it over a more mature option at the moment.

    I think we’re actually in complete agreement here.



  • Again, I don’t really see the difference here. Whether the authors continue to maintain the project long or not has little to do with what tools were used to build the project. And calling anything where LLMs are used for development vibecoding is just silly to be honest. There’s a huge variation in quality of code both in hand written code and that where LLMs are used. What you should be looking at in both cases is how much usage project gets, how good the tests are, whether authors built useful things before, and so on.

    If a project is useful then I really don’t care how it’s coded. Existing projects are in no way diminished by the fact that this project exists.