If AI is so good at coding - where are the open source contributions?
If AI is so good at coding - where are the open source contributions?
pivot-to-ai.com
If AI is so good at coding … where are the open source contributions?
96 comments
-
Have you used AI to code? You don't say "hey, write this file" and then commit it as "AI Bot 123 aibot@company.com".
You start writing a method and get auto-completes that are sometimes helpful. Or you ask the bot to write out an algorithm. Or to copy something and modify it 30 times.
You're not exactly keeping track of everything the bots did.
-
yeah, that's... one of the points in the article
-
I'll admit I skimmed most of that train wreak of an article - I think it's pretty generous saying that it had a point. It's mostly recounts of people complaining about AI. But if they hid something in there about it being remarkably useful in cases but not writing entire applications or features then I guess I'm on board?
-
-
Or to copy something and modify it 30 times.
This seems like a very bad idea. I think we just need more lisp and less AI.
-
I used it only as last resort. I verify it before using it. I only had used it for like .11% of my project. I would not recommend AI.
-
-
It’s not good because it has no context on what is correct or not. It’s constantly making up functions that don’t exist or attributing functions to packages that don’t exist. It’s often sloppy in its responses because the source code it parrots is some amalgamation of good coding and terrible coding. If you are using this for your production projects, you will likely not be knowledgeable when it breaks, it’ll likely have security flaws, and will likely have errors in it.
-
So you're saying I've got a shot?
-
And I'll keep saying this: you can't teach a neural network to understand context without creating a generalised context engine, another word for which is AGI.
Fidelity is impossible to automate.
-
-
If humans are so good at coding, how come there are 8100000000 people and only 1500 are able to contribute to the Linux kernel?
I hypothesize that AI has average human coding skills.
-
The average coder is a junior, due to the explosive growth of the field (similar as in some fast-growing nations the average age is very young). Thus what is average is far below what good code is.
On top of that, good code cannot be automatically identified by algorithms. Some very good codebases might look like bad at a superficial level. For example the code base of LMDB is very diffetent from what common style guidelines suggest, but it is actually a masterpiece which is widely used. And vice versa, it is not difficult to make crappy code look pretty.
-
"Good code" is not well defined and your example shows this perfectly. LMDBs codebase is absolutely horrendous when your quality criterias for good code are Readability and Maintainability. But it's a perfect masterpiece if your quality criteria are Performance and Efficiency.
Most modern Software should be written with the first two in mind, but for a DBMS, the latter are way more important.
-
-
Can Open Source defend against copyright claims for AI contributions?
If I submit code to ReactOS that was trained on leaked Microsoft Windows code, what are the legal implications?
-
what are the legal implications?
It would be so fucking nice if we could use AI to bypass copyright claims.
-
-
AI is at its most useful in the early stages of a project. Imagine coming to the fucking ssh project with AI slop thinking it has anything of value to add 😂
-
The early stages of a project is exactly where you should really think hard and long about what exactly you do want to achieve, what qualities you want the software to have, what are the detailed requirements, how you test them, and how the UI should look like. And from that, you derive the architecture.
AI is fucking useless at all of that.
In all complex planned activities, laying the right groundwork and foundations is essential for success. Software engineering is no different. You won't order a bricklayer apprentice to draw the plan for a new house.
And if your difficulty is in lacking detailed knowledge of a programming language, it might be - depending on the case ! - the best approach to write a first prototype in a language you know well, so that your head is free to think about the concerns listed in paragraph 1.
-
AI is only good for the stage when...
AI is only good in case you want to...
Can't think of anything. Edit: yes, I really tried
Playing the Devils' advocate was easier that being AI's advocate.I might have said it to be good in case you are pitching a project and want to show some UI stuff maybe, without having to code anything.
But you know, there are actually specialised tools for that, which UI/UX designers used, to show my what I needed to implement.
And when I am pitching UI, I just use a pencil and paper and it is so much more efficient than anything AI, because I don't need to talk to something, to make a mockup, to be used to talk to someone else. I can just draw it in front of the other guy with 0 preparation, right as it came into my mind and don't need to pay for any data center usage. And if I need to go paperless, there is Whiteboards/Blackboards/Greenboards and Inkscape.After having banged my head trying to explain code to a new developer, so that they can hopefully start making meaningful contributions, I don't want to be banging my head on something worse than a new developer, hoping that it will output something that is logically sound.
-
-
who makes a contribution made by aibot514. noone. people use ai for open source contributions, but more in a 'fix this bug' way not in a fully automated contribution under the name ai123 way
-
Counter-argument: If AI code was good, the owners would create official accounts to create contributions to open source, because they would be openly demonstrating how well it does. Instead all we have is Microsoft employees being forced to use and fight with Copilot on GitHub, publicly demonstrating how terrible AI is at writing code unsupervised.
-
-
Microsoft is doing this today. I can't link it because I'm on mobile. It is in dotnet. It is not going well :)
-
Yeah, can't find anything on dotnet getting poisoned by AI slop, so until you link it, I'll assume you're lying.
-
I guess they were referring to this.
-
-
-
My theory is not a lot of people like this AI crap. They just lean into it for the fear of being left behind. Now you all think it's just gonna fail and it's gonna go bankrupt. But a lot of ideas in America are subsidized. And they don't work well, but they still go forward. It'll be you, the taxpayer, that will be funding these stupid ideas that don't work, that are hostile to our very well-being.
-
Mostly closed source, because open source rarely accepts them as they are often just slop. Just assuming stuff here, I have no data.
-
And when they contribute to existing projects, their code quality is so bad, they get banned from creating more PRs.
-
To be fair if a competent dev used an ai "auto complete" tool to write their code, I'm not sure it'd be possible to detect those parts as an ai code.
I generally dislike those corporate AI tools but gave a try for copilot when writing some terraform script and it actually had good suggestions as much as bad ones. However if I didn't know that well the language and the resources I was deploying, it'd probably have led me to deep hole trying to fix the mess after blindly accepting every suggestion
-
They do more than just autocomplete, even in autocomplete mode. These Ai tools suggest entire code blocks and logic and fill in multiple lines, compared to a standard autocomplete. And to use it as a standard autocomplete tool, no Ai is needed. Using it like that wouldn't be bad anyway, so I have nothing against it.
The problems arise when the Ai takes away the thinking and brain functionality of the actual programmer. Plus you as a user get used to it and basically "addicted". Independent thinking and programming without Ai will become harder and harder, if you use it for everything.
-
People seem to think that the development speed of any larger and more complex software depends on the speed the wizards vsn type in code.
Spoiler: This is not the case. Even if a project is a mere 50000 lines long, one is the solo developer, and one has a pretty good or even expert domain knowledge, one spends the mayor part of the time thinking, perhaps looking up documentation, or talking with people, and the key on the keyboard which is most used doesn't need a Dvorak layout, bevause it is the "delete" key. In fact, you don't need yo know touch-typing to be a good programmer, what you need is to think clearly and logically and be able to weight many different options by a variety of complex goals.
Which LLMs can't.
-
-
Creator of curl just made a rant about users submitting AI slop vulnerability reports. It has gotten so bad they will reject any report they deem AI slop.
So there’s some data.
-
-
Ask Daniel Stenberg.
-
If AI was good at coding, my game would be done by now.
-
I am not a programmer and I think it's silly to think that AI will replace developers.
But I was working through a math problem in Moscow Puzzles with my kiddo.
We had solved it, but I wasn't sure he got it at a deep level. So I figured I'd do something in Excel or maybe just do cut outs. But I figured I'd try to find a web app that would do this better. Nothing really came up that was a good match. But then thought, let's see how bad AI programming can be. I'd fought with it over some excel functions and it's been mainly useful in pointing me in the right direction, but only occasionally getting me over the finish line.
After about 6 to 8 hours of work, a little debugging, havinf teach and quiz me occasionally, and some real frustration of pointing out that the feature previously changed and re-emeged, I eventually had something that worked.
The Shooting Range Simulator is a web-based application designed to help users solve a logic puzzle involving scoring points by placing blocks on vertical number lines.
A buddy developer friend of mine said: "I took a quick scroll through the code. Looks pretty clean, but I didn't dive in enough to really understand it. Definitely all that css BS would take me ages to do without AI."
I don't take credit for this and don't pretend that this was my work, but I know my kiddo is excited to try the tool. I hope he learns from it and we bond over a math problem.
I know that everyone is worried about this tool, but moments like those are not nothing. Personally, I'm a Luddite and think the new tools should be deployed by the people's livelihood it will effect and not the business owners.
-
Personally, I’m a Luddite and think the new tools should be deployed by the people’s livelihood it will effect and not the business owners.
Thank you for correctly describing what a Luddite wants and does not want.
-
-
AI is just the lack of privacy, Authoritarian Dragnet, remote control over others computers, web scraping, The complete destruction of America's art scene, The stupidfication of America and copyright infringement with a sprinkling of baby death.
-
As a dumb question from someone who doesn't code, what if closed source organizations have different needs than open source projects?
Open source projects seem to hinge a lot more on incremental improvements and change only for the benefit of users. In contrast, closed source organizations seem to use code more to quickly develop a new product or change that justifies money. Maybe closed source organizations are more willing to accept slop code that is bad but can barely work versus open source which won't?
-
Baldur Bjarnason (who hates AI slop) has posited precisely this:
My current theory is that the main difference between open source and closed source when it comes to the adoption of “AI” tools is that open source projects generally have to ship working code, whereas closed source only needs to ship code that runs.
-
That's basically my question. If the standards of code are different, AI slop may be acceptable in one scenario but unacceptable in another.
-
-
Maybe closed source organizations are more willing to accept slop code that is bad but can barely work versus open source which won’t?
Because most software is internal to the organisation (therefore closed by definition) and never gets compared or used outside that organisation: Yes, I think that when that software barely works, it is taken as good enough and there's no incentive to put more effort to improve it.
My past year (and more) of programming business-internal applications have been characterised by upper management imperatives to “use Generative AI, and we expect that to make you nerd faster” without any effort spent to figure out whether there is any net improvement in the result.
Certainly there's no effort spent to determine whether it's a net drain on our time and on the quality of the result. Which everyone on our teams can see is the case. But we are pressured to continue using it anyway.
-
I'd argue the two aren't as different as you make them out to be. Both types of projects want a functional codebase, both have limited developer resources (communities need volunteers, business have a budget limit), and both can benefit greatly from the development process being sped up. Many development practices that are industry standard today started in the open source world (style guides and version control strategy to name two heavy hitters) and there's been some bleed through from the other direction as well (tool juggernauts like Atlassian having new open source alternatives made directly in response)
No project is immune to bad code, there's even a lot of bad code out there that was believed to be good at the time, it mostly worked, in retrospect we learn how bad it is, but no one wanted to fix it.
The end goals and proposes are for sure different between community passion projects and corporate financial driven projects. But the way you get there is more or less the same, and that's the crux of the articles argument: Historically open source and closed source have done the same thing, so why is this one tool usage so wildly different?
-
Historically open source and closed source have done the same thing, so why is this one tool usage so wildly different?
Because, as noted by another replier, open source wants working code and closed source just want code that runs.
-
-
When did you last time decide to buy a car that barely drives?
And another thing, there are some tech companies that operate very short-term, like typical social media start-ups of which about 95% go bust within two years. But a lot of computing is very long term with code bases that are developed over many years.
The world only needs so many shopping list apps - and there exist enough of them that writing one is not profitable.
-
most software isn't public-facing at all (neither open source nor closed source), it's business-internal software (which runs a specific business and implements its business logic), so most of the people who are talking about coding with AI are also talking mainly about this kind of business-internal software.
-
There are commercial open source stuff too
-
-
I'll admit I did used AI for code before, but here's the thing. I already coded for years, and I usually try everything before last resort things. And I find that approach works well. I rarely needed to go to the AI route. I used it like for .11% of my coding work, and I verified it through stress testing.
-
I created this entirely using mistral/codestral
https://github.com/suoko/gotosocial-webui
Not a real software, but it was done by instructing the ai about the basics of the mother app and the fediverse protocol
-
I think it's established genAI can spit straightforward toy examples of a few hundred lines. Bungalows aren't simply big birdhouses though.
-
Still they're just birdhouses with some more infrastructure you can read instructions about how to build it.
-
-
-
To be honest, all of this is cope.
It's true that ai isn't a replacement for good coders ..YET.
But it will be. You all can be as mad as you want, publish as many articles about how much ai sucks as you want. but it won't stop anything from happening.
I say this as someone who has just started to learn to code myself.
The reason you all are mad is because you suddenly feel unsafe and unappreciated. And you're right.
Ai is still gonna happen though. It will take away a lot of your jobs (especially starting with jr coders just getting into the market). It will lower your pay. You can yell about it, or you can adapt. Sucks, but it is what it is.
Think of it this way: what do you think the market is gonna be like in 5 years? Then 10? Brah, start preparing now. Right fucking now. Cuz it ain't gonna get easier for you. I promise.
It happened with blue-collar factory works in the midwest regions of the US because of automation and offshoring. People removeded and tried to stop it. Lots of snooty white-color workers yelled, "learn to code!" But none of that saved their jobs.
And you guys won't stop it happening with your jobs either. I don't like the idea of AI taking over everything either. But it will. Adapt or die.
I've just started to learn to code. I am enjoying it. But in no way, shape, or form am I thinking it's going to lead to a job for me.
EDIT: To copy what some else said, much better than me:
The idea that AI will some day be good at coding isn’t the issue. The issue is that some people in management think it’s already well on the way to being a good substitute, and they’re trying to do more with fewer coders to everyone’s detriment.
-
The idea that AI will some day be good at coding isn't the issue. The issue is that some people in management think it's already well on the way to being a good substitute, and they're trying to do more with fewer coders to everyone's detriment.
-
To be honest, you sound like you're only just starting to learn to code.
Will coding forever belong to humans? No. Is the current generative-AI technology going to replace coders? Also no.
The reaction you see is frustration because it's obvious to anyone with decent skill that AI isn't up to the challenge, but it's not obvious to people who don't have that skill and so we now spend a lot of time telling bosses "no, that's not actually correct".
Someone else referenced Microsoft's public work with Copilot. Here's Copilot making 13 PRs over 5 days and only 4 ever get merged you might think "30% success is pretty good!" But compare that with human-generated PRs and you can see that 30% fucking sucks. And that's not even looking inside the PR where the bot wastes everyone's time making tons of mistakes. It's just a terrible coworker and instead of getting fired they're getting an award for top performer.
-
It's the Dunning-Kruger effect.
And it's fostered by an massive amount of spam and astroturfing coming from "AI" companies, lying that LLMs are good at this or that. Sure, algorithms like neural networks can recognize patterns. Algorithms like backtracking can play chess or solve or transform algebraic equations. But these are not LLMs and LLMs will not and can not replace software engineering.
Sure, companies want to pay less for programming. But they don't pay for software developers to generate some gibberish in source code syntax, they need working code. And this is why software engineers and good programmers will not only remain scarce but will become even shorter in supply.
And companies that don't pay six-figure salaries to developers will find that experienced developers will flat out refuse to work on AI-generated codebases, because they are unmaintainable and lead to burnout and brain rot.
-
To be honest, you sound like you’re only just starting to learn to code.
I definitely am. But I have no doubts that ai is going to take a lot of entry-level type jobs soon, and eventually higher end jobs.
We'll always need good, smart coders. Just not as many as we have now.
but it’s not obvious to people who don’t have that skill and so we now spend a lot of time telling bosses “no, that’s not actually correct”.
I get it. But those clueless people are gonna be the people in charge of hiring, and they'll decide to hire less, and expect current staff to do more. I've seen in hundreds of time in industries, and it's already happening now in yours.
For context, I'm old. So I've seen your arguments in many different industries.
And to your point, they'll have ai replacing good people, long before ai is good enough to. But you're approaching the issue with logic. Corporate lacks a lot of logic.
I'm already seeing it in your industry. Plenty of reddit/Lemmy posts talking about how coders have been laid off, and having a much much more difficult time getting another job than at any point in their careers.
Again, I'm saying AI is a good solution. I'm saying management will think that. Just like they did when they offshored jobs to much less skilled, yet way more inexpensive workers.
To copy what someone else in this thread said:
The idea that AI will some day be good at coding isn’t the issue. The issue is that some people in management think it’s already well on the way to being a good substitute, and they’re trying to do more with fewer coders to everyone’s detriment.
-
-
I think the biggest difference between this and blue-collars workers losing their jobs, though, is that the same people losing their jobs are also placed very to benefit from the technology. Blue collared workers losing manufacturing jobs couldn't, because they were priced out of obtaining that mafacturing hardware themselves, but programmers can use AI on an individual basis to augment their production. Not sure what the industry will look like in 10 years, but I feel like there will be plenty of opportunities for people who build digital things.
That being said, people who were looking to be junior developers exactly right now.... uhhh.... that's some extrememly unlucky timing. I wish you luck.
-
Well I'm old, so no looking for a job, I am just learning programming because i want to. But to your point, I am seeing LOTS of developers who have been laid off and finding another job is proving more challenging than ever before. It's rough out there and I feel for them.
To copy what someone else in this thread said:
The idea that AI will some day be good at coding isn’t the issue. The issue is that some people in management think it’s already well on the way to being a good substitute, and they’re trying to do more with fewer coders to everyone’s detriment.
-
They could now, because big "AI" companies sell their product on a loss.
The individual programmer is already outpriced when it comes to training those kind of models themselves. Once the companies want to turn a profit, the just laid off worker is outpriced as well. If an LLM can really do as good as a human programmer, who costs 70-100k, nothing stops the LLM provider to charge 35-50k easily. Try to augment your productivity at that price point, especially without a job.
I mean, society came through the change of the first and second work sector, we could reap the new productivity gains for the benefit of all, but, alas here we are at the beginning of a new crisis 😅
-
-
Do you think there's any reason to believe that these tools are going to continue their breakneck progress? It seems like we've reached a point where throwing more GPUs and text at these things is not yielding more results, and they still don't have the problem solving skills to work out tasks outside of their training set. It's closer to a StackOverflow that magically has the answers to most questions you ask than a replacement for proper software engineering. I know you never know if a breakthrough is around the corner, but it feels like we've hit a plateau for the foreseeable future.
-
Do you think there’s any reason to believe that these tools are going to continue their breakneck progress?
I do.
And as I mentioned in another comment, it's not so much that I think AI will do a better job, it's that I think MANAGEMENT will think AI does a cheaper job. Already many tech people who have been laid off are saying it's the worst job market they've ever seen.
AI sucks. But management is about dollars NOW. The are shortsided, fall into fads, and they will see the cost savings now as outweight the long term problems. I don't agree with them, I am saying they will do that tho. Even if we don't agree.
To copy what someone else in this thread said:
The idea that AI will some day be good at coding isn’t the issue. The issue is that some people in management think it’s already well on the way to being a good substitute, and they’re trying to do more with fewer coders to everyone’s detriment.
-
-
96 comments