true #vibecoding gives you no copyright to the end result, and at the same time exposes you for unknown liability for #copyright infringement. and if you promised to transfer copyright to the results to a client of yours, there's also a legal defect.
using #llms as dumb-ish auto-complete is mostly fine, but giving it autonomy is like copypasting random stuff from the internets and hoping for the best.
@km oh you mean what every developer has been doing with stack overflow the last ten years? ;-)
@marcus have they? i'd guess copypasting at least feels like cheating, no?
@km there’s a reason there are memes like these. ;-) I’m curious about the consequences for intellectual property on the long term. Setting aside the risk of accidental reuse of lgpl, would you say it’s risky for proprietary software to use public domain software parts in their products? Like including a public domain library in your closed source offering?
@marcus like this risky? otherwise, as long as you do what license says -- just go ahead. use and attribute, and -- ideally -- contirbute.
@km There's no attribution requirement for public domain code tho 🙂 But yea, all dependencies come with a risk and need to be evaluated.
