Replying to a post on minidisc.tokyo
@SuperDicq @lain Can you provide me with a checklist of do's and do not's for writing software going forward?
Replying to @sun@shitposter.world
@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.
Replying to @SuperDicq@minidisc.tokyo
@SuperDicq @lain @sun Personally, I'd argue that writing READMEs are the most mind-numbingly boring bit of writing software and rather one of the better use cases for an LLM.
Replying to @Phobos@eientei.org
@Phobos @lain @SuperDicq I also do admit that there is a systemic issue of what happens to the next generation of programmers who aren’t forced to learn things the hard way like I had to, but for me personally I don’t write any code a machine can now shit out ever again and that’s not actually a problem
Replying to @sun@shitposter.world
@sun @Phobos @SuperDicq @lain I wanna program for fun again* but I don't think I will use LLMs much. We'll see how that goes.
* I've been saying this for a while now but haven't really done anything.
* I've been saying this for a while now but haven't really done anything.
