> Even if we assume LLMs would consistently generate good enough quality code, code submitted by someone untrusted would still need detailed review for many reasons - so even in that case it would like be faster for the maintainers to just use the tools themselves, rather than reviewing someone else's use of the same tools.
Wouldn't an agent run by a maintainer require the same scrutiny? An agent is imo "someone else" and not a trusted maintainer.
Yes, I agree. It was just me playing with a hypothetical (but in my view not imminent) future where vibe-coding without review would somehow be good enough.
> I can still license that code to a company and ask them to pay me for using the code
I believe you can do that with public domain/copyright free material in general. There is no requirement to tell someone that the material you license them is also available under a different one or that your license is not enforceable.
Depending on how you do it and they find out, you could certainly be sued for fraud and misrepresentation, though. And, if you put a "copyright by me" at the top of a public domain work, it's technically a crime under 17 U.S.C. § 506(c) - Fraudulent Copyright Notice
I remember the case of books used for training, where the court found training to be fair use, but the material has to be legally obtained (=Bought instead of pirated the books).
I think you nailed it here. What you are "licensing" with your license is copyright. But if training is fair use, copyright doesn't apply, so there is no need for a license.
It can also be 3 people, as one person can be a father and a son at the same time. If you allow non-mentioned people to be included in the attribute (i.e. the sons of the fathers are not part of the 2) it could also be 2 people, as long as they are fathers.
That's interesting as my first thought reading the comments was "this problem seems very similar to many students writing papers just finding citations that sound correct".
Sometimes it is really sad to read from (even PhD level) students on social media about their paper writing practices.
We might remember the last 40 years differently, I seem to remember data centers requiring power plants and part shortages. I can't check though as Google search is too heavy for my on-plane wifi right now.
Even ignoring the cryptocurrency hype train, there were at least one or two bubbles in the history of the computer industry that revolved around actually useful technology, so I'm pretty sure there are precedents around "boasting about part shortages" and desperate build-up of infrastructure (e.g. networking) to meet the growing demand.
> Looking forward to the NALs responding why this is terrible.
My NAL guess is that it will go a little like this:
* Candidate makes disparaging post on reddit/HN.
* Gets many responses rallying behind him.
* Company (if they notice at all) sues him for breach of Non-Disparagement-Agreement.
* Candidate makes followup post/edit/comment about being sued for their post.
* Gets even more responses rallying behind him.
Result: Company gets $10.000 and even more damage to their image.
(Of course it might discourage some people from making that post to begin with, which would have been the goal. You might never try to enforce the NDA to prevent the above situation. Then it's just a question of: Is the effort to draft the NDA worth the reduction in risk of negative exposure, when you can simply avoid all of it by not providing feedback.)
Wouldn't an agent run by a maintainer require the same scrutiny? An agent is imo "someone else" and not a trusted maintainer.