Hello,
the limit and tentation to jump between these "simple" use cases to the
one you dont want is VERY thin and fragile.
This is on purpose, these tools are addictive and made specifically so
the user will jump.
From my point the only way to avoid entirely predictable problems is to
just avoid the cause of such problems, to the extent possible by the
common maintaining team.
And I also know that it is impossible.
<off topic>
I hate AI so much.
It is a known and documented regression of human intelligence, but so
many money is in question that capitalism just wins over humanism.
Sebastien
On 2/4/26 10:11, raiden00pl wrote:
My approach to AI:
- AI as a general support tool - OK.
- AI for generating test cases that don't make it to the upstream - OK.
- A short PR summary after human review - OK.
- Improving documentation after human review - OK.
- Many other cases where AI actually boosts productivity - OK
BUT, AI as a tool for writing entire code modules without serious security
and licensing analysis - unacceptable (but I think we haven't encountered
this problem yet).
