Earlier quoted context omitted.
I agree with you on the policy being balanced. However: > AI generated code does not substitute human thinking, testing, and clean up/rewrite. Isn't that the end goal of these tools and companies producing them? According to the marketing[1], the tools are already "smarter than people in many ways". If that is the case, what are these "ways", and why should we trust a human to do a better job at them? If these "ways"…
Intern generated code does not substitute for tech lead thinking, testing, and clean up/rewrite.
AI Usage Policy
101–110 of 293 posts
Re: AI Usage Policy
#102Interesting requirement! Feels a bit like asking someone what IDE they used.
There shouldn't be that meaningful of a difference between the different tools/providers unless you'd consistently see a few underperform and would choose to ban those or something.
The other rules feel like they might discourage AI use due to more boilerplate needed (though I assume the people using AI might make the AI fill out some of it), though I can understand why a project might want to have those sorts of disclosures and control. That said, the rules themselves feel quite reasonable!
Re: AI Usage Policy
#103A good PR using IA should be impossible to distinguish from a non-AI one.
The problem is that most aren’t good, and bad ones can take a lot of effort to distinguish, if they look plausible on the surface. So the potentially good ones aren’t worth all the bad ones.
Re: AI Usage Policy
#104Earlier quoted context omitted.
Problem is people seriously believe that whatever GPT tells them must be true, because… I don't even know. Just because it sounds self-confident and authoritative? Because computers are supposed to not make mistakes? Because talking computers in science fiction do not make mistakes like that? The fact that LLMs ended up having this particular failure mode, out of all possible failure modes, is incredibly unfortunate…
I think in science fiction it’s one of the most common themes for the talking computer to be utterly horribly wrong, often resulting in complete annihilation of all life on earth. Unless I have been reading very different science fiction I think it’s definitely not that. I think it’s more the confidence and seeming plausibility of LLM answers
Re: AI Usage Policy
#105A factor that people have not considered is that the copyright status of AI generated text is not settled law and precedent or new law may retroactively change the copyright status of a whole project. Maybe a bit unlikely, but still an issue no one is really considering. There has been a single ruling (I think) that AI generated code is uncopyrightable. There has been at least one affirmative fair use ruling. Both of…
This only matters if you get sued for copyright violation, though.
You may become a big enough target only when it's too late to undo it.
Re: AI Usage Policy
#106See x thread for rationale: https://x.com/mitchellh/status/2014433315261124760?s=46&t=FU... “ Ultimately, I want to see full session transcripts, but we don't have enough tool support for that broadly.” I have a side project, git-prompt-story to attach Claude Vode session in GitHub git notes. Though it is not that simple to do automatic (e.g. i need to redact credentials).
Re: AI Usage Policy
#107Earlier quoted context omitted.
> The biggest surprise to me with all this low-quality contribution spam is how little shame people apparently have. ever had a client second guess you by replying you a screenshot from GPT? ever asked anything in a public group only to have a complete moron replying you with a screenshot from GPT or - at least a bit of effor there - a copy/paste of the wall of text? no, people have no shame. they have a need for a l…
Problem is people seriously believe that whatever GPT tells them must be true, because… I don't even know. Just because it sounds self-confident and authoritative? Because computers are supposed to not make mistakes? Because talking computers in science fiction do not make mistakes like that? The fact that LLMs ended up having this particular failure mode, out of all possible failure modes, is incredibly unfortunate…
Re: AI Usage Policy
#108The biggest surprise to me with all this low-quality contribution spam is how little shame people apparently have. I have a handful of open source contributions. All of them are for small-ish projects and the complexity of my contributions are in the same ball-park as what I work on day-to-day. And even though I am relatively confident in my competency as a developer, these contributions are probably the most thoroug…
> The biggest surprise to me with all this low-quality contribution spam is how little shame people apparently have. ever had a client second guess you by replying you a screenshot from GPT? ever asked anything in a public group only to have a complete moron replying you with a screenshot from GPT or - at least a bit of effor there - a copy/paste of the wall of text? no, people have no shame. they have a need for a l…
Re: AI Usage Policy
#109Earlier quoted context omitted.
People's trust on LLM imo stems from the lack of awareness of AI hallucinating. Hallucination benchmarks are often hidden or talked about hastily in marketing videos.
[flagged]
It's like a JPEG. Except instead of lossy compression on images that give you a pixel soup that only vaguely resembles the original if you're resource bound (and even modern SOTA models are when it comes to LLMs), instead you get stuff that looks more or less correct but just isn't.
Re: AI Usage Policy
#110Earlier quoted context omitted.
> The biggest surprise to me with all this low-quality contribution spam is how little shame people apparently have. ever had a client second guess you by replying you a screenshot from GPT? ever asked anything in a public group only to have a complete moron replying you with a screenshot from GPT or - at least a bit of effor there - a copy/paste of the wall of text? no, people have no shame. they have a need for a l…
Not OP, but I don't consider these the same thing. The client in your example isn't a (presumably) professional developer, submitting code to a public repository, inviting the scrutiny of fellow professionals and potential future clients or employers.
They are sure they know better because they get a yes man doing their job for them.