[–] 4 points 2 months ago (1 child)

For me, if a PR looks good, and I can reach out to the contributor and they can competently discuss their work, then its fine with me if they used AI to code it.

I think a sensible policy would be: use whatever tools you like to contribute, but own the contribution. Obvious slop code is rejected.

  • source
  • parent
  • context
  • [–] 2 points 2 months ago

    I agree, human vetting from experience is essential. But with agenetic, tool calling LLMs, you can (and should IMO) require multiple solutions be explored and presented with the tradeoffs for each option clearly outlined, and wait for you guidance to proceed with the advisee approach.

    LLM can definitely be used to churn out garbage code based on the averaging of everything, but can also be a super useful tool, if used effectively, to quickly see the most common ways a problem is solved, and then design and iterate a solution that works for your project.

    Similar to how I used to use SO, but with reasoned reviews of all the posted solutions and the ability to prototype what might work best for what I need.

  • source
  • parent
  • context
  • [–] 3 points 8 months ago (1 child)

    OK, if your talking homebrew on Mac, then your not just doing "basic" things. yes, for power users on Linux, we need to use the CLI. For actual basic things (browsing, word processing, consuming media) you absolutely don't need to touch it at all on many "noob" distros.

    So claiming that there's a steep learning curve for basic things is going to turn off new users, who would be perfectly fine never looking at a terminal to do what they need

  • source
  • parent
  • context
  • view more: next ›