• 0 Posts
  • 8 Comments
Joined 3 years ago
cake
Cake day: June 1st, 2023

help-circle




  • The problem isn’t what can be done, the problem is what is being done. An AI in hands of a good developer can make that developer better - sure.

    On the other hand what actually happens is equivalent to submitting code that doesn’t compile, except it’s not quite as easy to discover. The code does compile but it often is still bogus. Maybe it doesn’t solve the issue, maybe it does but in a round-about way, etc.

    Legal and economical arguments aside I’m not saying “don’t use AI” - I’m saying “if you submit AI code - verify its work before making someone else verify its work”. And that means you need to know how to verify its work - just compiling and running isn’t enough.



  • The problem is that FOSS projects that are popular already have a a high quality standard because they are developed by very smart people who’s been developing for a long time.

    There is inherently a problem with current AI - It doesn’t learn.

    When a new developer joins a FOSS project they first spend weeks or even months learning this project’s specific coding practices, standards, and reasoning. I’ve been programming for 20 years and have a PhD. I can’t “just start contributing” to something like KDE because I’ve never looked at its codebase. I don’t know assumptions, methodology, or challenges that are baked into the codebase. I need to spend time to learn those to be a useful contributor.

    AI can’t learn unless you do gradient descend. The problem that you mention about sounding elitist is that those FOSS developers spend a good amount of their time training new contributors and everyone is proud of their work. Now you have people who are not ready to be contributors tell AI to contribute and it’s doing its best but it just can’t learn and even having a 200K token context is not enough to fit all those project specific assumptions and rhetorics in.