Egregoros

Signal feed

Timeline

Post

Remote status

Context

24

@sun@shitposter.world @lain@lain.com The problem is that output from LLMs currently has a legally ambiguous status. You can not risk integrating it into any existing free software right now, so that's why a lot of projects, with some exceptions, choose not to allow it or heavily limit its usage only to specific tasks.

And on a personal note I think obvious LLM output is extremely tasteless. Seeing someone not even use some effort to at least even write their own README file makes me cringe. I always compare it to the same type of feeling you get when you see a corporate logo which uses Comic Sans.

@lain @Phobos @SuperDicq @besserwisser @sun @mischievoustomato You learn barely anything in the process. LLMs are great for newbies to get started and explain stuff as you go. Mostly because you bypass knowledge gatekeepers and nonexistent docs. But if you let it do everything from the start, you won't get that most likely.

In order to use LLMs for "make XYZ, make no mistakes or you go to jail", you have to know how things are supposed to look and work to at least tell it to fixup what it did wrong. And you won't have that experience if you don't have at least some background.

GitHub is a great example when you let everyone aislop a site with barely any experience when most of the original devs left. It's basically unusable now, even if you ignore the frequent downtime. Back navigation half works, switching issues/PRs/code tabs does not work most of the time,...