I agree. Disclosure of A.I. use should be mandatory.
My main concern with A.I. use is its ability to hide incompetence. If a new agent introduces code that was entirely written by illegal-software that violates copyright law–A.I.–then that should be made clear, even if competent-programmers review the new inclusion and approve of it. Otherwise people are left with the impression that this new agent is a competent programmer. A.I. use–undisclosed–creates false reputations.
The disclosure being encouraged and not mandatory is purely to protect the egos of programmers currently utilizing A.I. products.
However I do respect their decision and I maintain projects should be self governing.
I disagree. For one, it’s unenforceable, just like outright banning it.
But AI assistance can also mean a lot of different things, from outright vibecoding through autocomplete up to only asking it to so review. It diminishes the human work in the eyes of other people, because a simple disclaimer doesn’t distinguish between the work done, and also encourages people to point out to AI as a scapegoat for their mistakes.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it’s crap it doesn’t absolve you that you didn’t use AI…
It’s a tool, so use it responsibly like any other tool and stand behind your code no matter what tools you used.
I disagree. For one, it’s unenforceable, just like outright banning it.
Agreed. I an aware a lot of people contributed to the Linux kernel, without disclosing they used ai.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it’s crap it doesn’t absolve you that you didn’t use AI…
Yeah. I do not blame the ai for writing the code, but rather the person to accept and push that code even if they know it is crap.
I do respect their decision and I maintain projects should be self governing.
Me too, but I also think that governance isn’t as simple as “we get to decide what we do”, it also interacts with how well the decision-makers understand their domain and their broader it sits in, both of which are potentially reduced as a consequence of relying on AI.
Also there is the possibility of AI tools dominating workflows and then getting ripped away (either as the corporates raise costs, or the bubble bursts and they collapse), leaving a project overwhelmed with a unmanageably large array of weaknesses. In that scenario self-governance starts to become irrelevant.
I agree. Disclosure of A.I. use should be mandatory.
My main concern with A.I. use is its ability to hide incompetence. If a new agent introduces code that was entirely written by illegal-software that violates copyright law–A.I.–then that should be made clear, even if competent-programmers review the new inclusion and approve of it. Otherwise people are left with the impression that this new agent is a competent programmer. A.I. use–undisclosed–creates false reputations.
The disclosure being encouraged and not mandatory is purely to protect the egos of programmers currently utilizing A.I. products.
However I do respect their decision and I maintain projects should be self governing.
I disagree. For one, it’s unenforceable, just like outright banning it.
But AI assistance can also mean a lot of different things, from outright vibecoding through autocomplete up to only asking it to so review. It diminishes the human work in the eyes of other people, because a simple disclaimer doesn’t distinguish between the work done, and also encourages people to point out to AI as a scapegoat for their mistakes.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it’s crap it doesn’t absolve you that you didn’t use AI…
It’s a tool, so use it responsibly like any other tool and stand behind your code no matter what tools you used.
https://deadsimpletech.com/blog/no-such-thing-as-just-a-tool
If people thought “its impossible to catch everyone so why bother trying to catch anyone at all” when making laws, no laws would exist
THIS, THIS, THIS
Basically, a nirvana fallacy/perfect solution fallacy.
Agreed. I an aware a lot of people contributed to the Linux kernel, without disclosing they used ai.
Yeah. I do not blame the ai for writing the code, but rather the person to accept and push that code even if they know it is crap.
Me too, but I also think that governance isn’t as simple as “we get to decide what we do”, it also interacts with how well the decision-makers understand their domain and their broader it sits in, both of which are potentially reduced as a consequence of relying on AI.
Also there is the possibility of AI tools dominating workflows and then getting ripped away (either as the corporates raise costs, or the bubble bursts and they collapse), leaving a project overwhelmed with a unmanageably large array of weaknesses. In that scenario self-governance starts to become irrelevant.