Thread

Pop!_OS bans AI-generated code from much of its codebase

116 points · 167 comments · bundie

lkramer · 1791054466 · focus · HN ↗
I had a PR in flight that got closed because of this. I had an issue with passwords in the network applet for the VPN and had used Claude to help me identify and then come up with a fix. I did spend a lot time handcrafting and making sure the quality was good, but I respect their decision and no hard feelings, but as someone who have struggled to find time and opportunity to contribute to open source it was a small set back.
1. sedan_baklazhan · 1791055796 · focus · HN ↗
  What is actually the meaning of “handcrafting” here?
  1. lkramer · 1791068202 · focus · HN ↗
    What I meant by it was that I read every line of code generated, made sure I understood its purpose and either manually rewrote it if I felt there was a better way or asked Claude to do it. E.g. there was a bug where the password could end up in a configuration labelled as a username. Claude's initial fix was to simply exclude 'username' in a for loop, but I asked it to find examples in similar code in other codebases to see what the best practice was and ended up basing to fix on what is done in Gnome.
    sedan_baklazhan · 1791094930 · focus · HN ↗
    Can you show the PR?

Unofficial Hacker News client; not affiliated with Y Combinator.