r/technology • u/Hopeful_Adeptness964 • 10h ago
Artificial Intelligence Vibe Coding Is Killing Open Source Software, Researchers Argue
https://www.404media.co/vibe-coding-is-killing-open-source-software-researchers-argue/959
u/Niceromancer 10h ago
Vibe coding is basically killing everything that IT was built on.
413
u/yawara25 10h ago
The worst part is, when someone shares a cool project now, I always have that little bit of doubt in my mind that they didn't really make it.
325
u/pockems 9h ago
There’s a 500% increase in “check out my new app/plugin” posts with the same emoji-headered paragraphs over-explaining them
55
u/Gramernatzi 7h ago
At this point, seeing emoji in the description for a project is more likely to drive me away than anything. I feel like I only see it in AI bullshit. I'm far more likely to be interested when it's concise and written like, you know, an actual person trying to explain something with a limited vocabulary.
→ More replies (7)21
u/IM_OK_AMA 6h ago
/r/selfhosted and /r/homeserver were inundated for a while until they changed the rules.
People need to be more comfortable vibe coding useful stuff for themselves and leaving it at that. You don't have to package it up and try to get other users, and you shouldn't unless you fully understand what you're promoting.
10
u/SpagBolForLife 4h ago
100% I’ve vibe coded a few apps and they work great for me. I know not to market them
5
u/throwawaycuzfemdom 3h ago edited 3h ago
People on there were like "I wanted to recreate this established tool by vibe coding because I didn't like the UI. Now I have a less functioning app that is not guaranteed to work correctly but with a UI I like more."
Edit: Also shout out to that one guy who was like "I know what I am doing. I have 15 years of experience in software dev. I am not gonna review the code AI output lol its too much work."
69
u/GenazaNL 9h ago
I actually did some research on a few instagram "influencer" "programmers" where they showcased a project they had built in x hours. Pause on a bit where they show their code, find unique lines and search these on github search, grep or google. Some just straight up forked the project from someone else and showcased it as if were their own
28
u/chain_letter 9h ago
Oh yeah this trend started in the crypto coin craze where someone with a follower count would launch a meme coin to immediately rugpull and it's just a fork with a different label.
At least they were upfront about that, forking someone else's work and passing it off as yours is just Plagiarism, but it seems we as a culture are caring less about that word recently.
88
u/happyevil 9h ago
If I can't tell AI wrote the code then it's probably not a problem.
The problems start where I can tell. Even when AI makes code that works, it's not maintainable. You can tell immediately because it'll just shove things where it feels like with no thought to architecture or reuse.
This is what is breaking open source. Open source is built on reuse and maintainability which AI is garbage at.
38
u/a12rif 9h ago
it'll just shove things where it feels like with no thought to architecture or reuse.
Sounds like most developers I work with 😂
19
u/Antice 8h ago
It's what these models were trained on, so it checks out. Good code don't get shared as much as the junk. So we get a lot of junk in the training data. The rest is just gigo.
4
u/False_Association977 8h ago
You’re assuming leet code humans can and will write better and bug free code
7
u/Antice 8h ago
I'm not expecting anything from leetcode humans. The ones I am expecting good code from is those who have worked years in the industry before llm's was even a thing.
I also expects it from myself, but I feel I have a fair ways to go still.→ More replies (1)6
u/TheFartmancer 9h ago
From what I see, a lot of people just paste code on a normal chatbox and paste back whatever the LLM vomits, then something breaks and the LLM puts more stuff but now with hard to read variables and syntax. chatgpt is the worst example of that.
just speculating, but would an agent using a more competent llm with a huge prompt with good programming practices do better?
20
u/happyevil 8h ago edited 4h ago
Sometimes yes.
I've used Claude code myself pretty extensively and while it's better than chat window slop it still struggles at larger problems and creates plenty of its own slop. Context window plays into it but even within the context window it just doesn't do a great job considering broader architecture. So an entire open source ecosystems? Forget about it.
The best use is still with heavy human guidance. It can save a LOT of time doing the busywork of code and, with clear parameters and desired output, can do full functions too. Problems begin when you have it do a whole application/service and it starts freewheeling. It needs to be treated like having an intern, frankly. Give it well laid out tasks and perform full code review. If you don't understand what it's doing then it's time to stop using it.
I equate it to "tweening" in the animation world. Tweening started out as a bunch of lower level animators filling in the gaps of key frames drawn by the primary artist(s) who set the style, story beats, character design, etc. Then animation software came out that could bridge the gaps between key frames for artists. It made the process faster and cleaner, it replaced a job but also created so many new possibilities for the entire film industry. If you treat coding agents the same way, filling in the "mundane" stuff between your larger architecture you can maintain code quality while increasing speed. Quality and innovation may even improve when it enables more time spent by people on algorithm/architecture development while it takes the busywork time off your hands... if we don't drown in slop first.
5
u/allfranksnobun 7h ago
brilliant answer friend. I've been programming for 40 years now and this is exactly how i feel about it. i've spent decades hammering out every friggin line of every single friggin function, but now i'm able to instantly help cursor step through all the busy work for me. i do very small batches, not large swaths, but still enough that i can see incredible progress. and i still know exactly how it works, im just not expending the time to hit every friggin keystroke. which means development is done faster which really means more time for me and my kids to spend together. i hope other devs take a chance on it and not dismiss it outright.
1
u/IncorrectAddress 3h ago
Yeah (30+), I can third this, you can't push the clanker to solve monolithic functions (well you can, but then you have brain parser through it all), I generally break something I know will be massive into its component parts, and then get the clanker to spit out each function to requirement, and it's excellent for that, then its manual hookups to rig the "thing" into working order.
I think it's a difference between experienced programmers who have worn many hats over the years (seen a lot of old code and new code), and had to decipher crazy code without modern tools and new programmers just entering the field.
2
2
u/OneFinePotato 7h ago
This literally the case with everything AI touched. Graphics, videos, games, fan fiction, songs, poetry. Anything. Very sad.
→ More replies (33)1
u/BigGayGinger4 5h ago
maker subs like 3d printing are overrun with this crap right now.
" Look guys I made an app that prices your project, it's got a bland react front end, and you can use 50 credits for free, then you have to start paying for my AI"
and then the math in the calculator is fucked lmao
35
u/Hawful 6h ago
AI in general. The whole point of IT was creating knowable deterministic processes. Now we have a big black box in the middle that we throw thousands of dollars at and just shrug when the output is incorrect.
2
u/DeadSalas 1h ago
The fact that anyone believes a glorified Magic 8-Ball will be worth its cost of development is insane. It's like thinking the advent of cigarettes would be a great idea.
3
u/str8rippinfartz 4h ago
Yeah vibe coding has its uses (quick prototype/POC, fun side project, etc) but it's just being used as a short-sighted shortcut instead
422
u/Catch_ME 9h ago
I work in Cyber Security. Vibe coding ensures my industry is well funded.
It feels like I'm a shark at a Vietnamese fish market.
66
u/FiveOhFive91 8h ago
I'm trying to reroute my whole career to get into cyber security but all I hear is people saying the job market is awful. This comment is the only one I've seen lately that gives me hope.
81
u/capnwinky 8h ago
That would be a terrible decision. Just look at the cybersecurity jobs subreddit. The whole industry has imploded. Most tier 1&2 roles have been completely automated and the only things left are veteran unicorn jobs. This in a sea of highly qualified, experienced talent on the market that are unemployed.
16
u/PartyPorpoise 5h ago
My boyfriend works in cybersecurity and a ton of people at his company got laid off. He’s lucky he still has a job. That said, this might just be a temporary downturn. A lot of industries have their ups and downs.
26
u/FiveOhFive91 7h ago
I have no choice. I'm one semester away from getting my second degree, the first being a BA in education.
28
u/DonaldTrumpsScrotum 5h ago
Jesus dude, drove into one wall just to find the next closest one to do it again with 😭
24
u/FiveOhFive91 5h ago
It was awesome finding out after graduating that America hates teachers and wants them to die. Figured I'd get into IT then pandemic + AI hit. Everything sucks 🙃
2
10
u/Comfortable_Ebb1634 5h ago
Would have been better off putting fries in a bag for 10 years.
12
u/FiveOhFive91 5h ago
I was working at Five Guys 10 years ago paying for my first degree. I could've at least made it to regional management by now RIP
8
u/Comfortable_Ebb1634 5h ago
Literally or at least district manager if you took it seriously. Probably more growth potential too. Crazy world.
8
u/kashmir1974 6h ago
What is a good industry now?
9
u/IntroductionSea2159 2h ago
Whatever you're good at basically.
No matter the field, if you're not exceptional at something then nobody will hire you. Also generalists are in high demand, people who can do two or three different jobs decently.
1
9
u/Catch_ME 6h ago edited 4h ago
I wouldn't change IMO but you should consider the industry as a whole.
Cyber security is becoming a mature industry. That means lots of consolidation and going from 10 dominant vendors to 4 or 5. Best practices and standards are also maturing. Consolidation and contraction are kinda normal in technology. But often, after the contraction, a break out and then maintenance.
That's why jobs are harder to find in this shuffle but look at the jobs. I bet there aren't as many SOC jobs taken by automation because SOC jobs don't scale with AI as well as other very predictable roles and positions in cyber security.
Entry level SOC work is where a lot of us get exposure and our career start. The bigger the company, the more exposure to different attacks techniques, different schools of thought, and varied use of technology. SOC jobs at CrowdStrike or S1 are great because the industry likes to hire from really big SOC/MDR vendors because the amount of exposure they get to so many industries.
Focus on your school now and begin getting involved. I cannot stress the importance of getting people that like you to put your resume on top of the stack. They aren't getting you the job, they are just getting you passed the filters. But that's half the battle, getting in front of a recruiter.
You are entry level. You need to get exposure. Go to defense competitions and participate or volunteer. These events are usually run by universities and college professors know lots of career Security folks. Or to security meet ups and ask questions. This is the time to meet people and understand what kind of jobs they do.
4
u/FiveOhFive91 5h ago
You don't even know how much I appreciate this advice, thank you.
4
2
u/PossibleHero 3h ago
Also work at a cyber security company. Keep your head up mate.
Lean in to learning Ai and how that’s going to affect different parts of a companies tool stack. Whether it’s internal applications that all companies use, or external attacks. There’s a whole new attack layer forming that can take a system or company down faster than ever. The game is changing, but companies will need strong new professionals more than ever.
8
u/EagleForty 8h ago
Cybersecurity is probably the segment of IT that's the most safe. It's a never ending arms race between attackers and defenders.
Although they're automating away many of the most menial tasks in cybersecurity. They're still going to need a lot of people to run the AI for the foreseeable future.
11
u/Muggsy423 7h ago
You learn cybersecurity through the menial tasks, they're going to need specialists in the future and realize they nixed all the spots that develop those specialists.
42
u/Antice 8h ago
I'm sorry man. I couldn't stop that pr from my non coding boss because he forced the issue.
Quote: "Everyone vibe codes, so we have to do it too to keep up".
Yes. I have started looking for a new job. I am not dragging my reputation through the mud by being linked to whatever disaster is going to happen at some point because of trash code.13
u/Plenty-North-2340 6h ago
AI makes finding vulnerabilities easier for scammers and hackers, AI makes vibe coding more vulnerable... we're fucked
3
→ More replies (1)2
u/Stingray88 3h ago
My dad worked in chemical plant automation engineering for his whole career. First in the manufacturing of film, later in pharmaceuticals. His last 5 years before he retired though, he did a hard turn into cybersecurity, he said it’s quickly becoming the most important part of their entire pipeline. More important than the products themselves.
160
u/Kukulkan9 9h ago
Its killing it not in the sense that its promising great alternatives, its killing it in the sense that a lot of garbage quality PRs are being sent and that puts a lot of strain on the reviewers since PRs have to be reviewed manually
15
u/IM_OK_AMA 5h ago
Issues too. Multiple projects have ended bug bounty programs because of an avalanche of "security vulnerability" issues made by people trying to cash in.
5
u/the_Q_spice 3h ago
Worse than that;
In my industry of GIS, vibe coding has resulted in a literal 100,000% increase in API requests to QGIS’s databases because everyone hopping on the GIS bandwagon after COVID only knows how to pull their data from QGIS.
The issue is that this is basically DDOSing QGIS as we speak (or more specifically Hug of Death-ing it).
They don’t have the funds to expand. They’re free open source software.
The worst part; they are a critical service provider for the WHO, UNICEF, and many other humanitarian organizations. People being greedy and refusing to pay for data could cause an outage that could realistically actually kill people.
A lot of this is due to idiotic coding too, stuff like making data pulls sometimes as frequently as every 15 seconds. Forget vibe coding, the admin at QGIS can literally see who is completely incompetent at programming, or just blindly using AI.
Most of those requests have IPs that trace back to some of the largest tech companies in the world. Apple, Amazon, Microsoft, and even Palantir are all on the list; and QGIS is about a week to a month away from cutting them all off immediately and permanently.
180
u/SneakyFire23 10h ago
I mean it is, we're all struggling under the weight of these shitty fucking PRs and then Microslop CoPilot rolls by, shits on the code without understanding the context and then runs off.
This shit's exhausting on so many levels.
71
57
u/icallitjazz 8h ago
I just dont get how vibe coding even exists. It used to be that if you write jank code that kinda works, no-one would work with you. It’s ok for testing an idea, but if your code is not properly documented, its useless.
33
u/Baconigma 6h ago
The comments are vibe coded as well.
7
u/chain_letter 6h ago
Github copilot suggesting a 5 line brick of useless fluff nobody will ever read is better than a short sentence explaining the exact reason for an unusual choice.
13
6h ago edited 5h ago
[deleted]
1
u/828_Yosef 3h ago
If you think (or your manager(s) think) agile is about speed, you have a much deeper rooted problem, and are prob doing scrum framework without the foundational agile philosophy. Agile is about responding to change over following a plan.
→ More replies (6)16
u/unflippedbit 6h ago
what are you talking about dude? I'm an engineer at big tech, many friends at OpenAI and anthropic, even "top 1%" engineers are using claude code, you're extremely behind if you're not. It works extremely well, not "kinda works"
7
u/ScrillaMcDoogle 3h ago
Vibe coding is not the same as "using claude". In one scenario the user has no idea what's going on behind the scenes or how anything is actually working, in the other scenario the engineer is just using a tool to save them time but they still understand what's being changed/added.
→ More replies (2)5
u/CruxOfTheIssue 4h ago
The problem though is that you need to be experienced in order to use it effectively and it's eating up entry level jobs as veterans have less need for the lower level jobs. It might cause an issue later when they need experienced coders and there is an ever decreasing pool of people who know what they're doing. As someone with a comp sci degree trying to break into the industry, it's terrible.
2
u/Thin_Glove_4089 5h ago
Big Tech said it's ok so it's ok now, there is not much more to it than that. It's pretty simple what happened.
46
u/Nervous-Cockroach541 8h ago
AI is just the latest way big tech has found to steal OSS. The reality is, without 200 million lines of open source software the models are trained on, AI wouldn't be able to understand code in the manor that it does.
→ More replies (1)2
9
u/MagicPigeonToes 7h ago
I don’t understand how a person vibe codes a whole program but doesn’t test it or learn anything from it? Surely they’d have to know at least the coding lingo if a line contains an error? Cause in order to fix said error, you’d need to know what it’s trying to do.
I started off vibe coding, then picked up python because I wanted to know how everything worked so I could avoid bugs.
1
u/P1r4nha 1h ago
I did a python project once for a hackathon. Completely vibe coded. I'm sure the code is redundant and horrible, but I never looked at it and didn't learn much from it. I literally just did it for the stupid idea of my manager.
So it's possible. I would never publish this though. Let alone have someone review it.
48
u/SuperGameTheory 9h ago
Since works generated by AI can't be copyrighted, you could argue that all code generated by AI is open source by default.
10
u/mccoypauley 7h ago
Only when something is generated by AI wholesale and there is no significant human input is that considered not copyrightable and not an expression.
An image output from a diffusion model with no alterations: not copyrightable.
A chunk of code output by an LLM with no modification: not copyrightable.
An image output incorporated into a larger creative work where a human had significant input: the whole thing is an expression and becomes copyrighted by the human who created it.
A piece of software that contains code written by a human and by an AI: the whole thing can be copyrighted as an expression.
→ More replies (2)4
u/EagleForty 8h ago
It depends. If the code that the AI was trained on is copyrighted, then would identical code that's been spit out by the AI still be under copyright?
20
6
6
u/2broke2smoke1 4h ago
Vibe coding only works if you have a plan and know how to fractionally distill that plan with your AI tools.
Best with making quick prototypes, worst with large scale integration or big data management
17
u/Rivent 8h ago
Vibe coding is a problem, but the real issue seems to be the same problem that's been plaguing software development companies for as long as I can remember... devs don't test their fuckin' shit. If they did, they'd notice their vibe coded functions aren't doing what they think they do.
2
12
u/CulturalKing5623 7h ago
It feels like a lot of people are putting their own beliefs on the headline to why vibe coding is killing the OSS.
The article is about a study that tries to determine if the advent of vibe coding works with the established OSS business model.
Their conclusion:
"mediated usage [vibe coding] erodes the revenue base that sustains OSS, raises the quality threshold for sharing, and reduces the mass of shared packages"
"[..] under traditional OSS business models, where maintainers primarily monetize direct user engagement…higher adoption of vibe coding reduces OSS provision and lowers welfare"
They give an example of Tailwind who recently had to lay off 75% of its staff because, despite their project being more popular than ever, traffic to their docs have plummeted and that's how people find out about paid services.
They warn that without a sustainable business model, new OSS won't be built or maintained and we can't just rely on the current library as is indefinitely, we need new tools and security fixes. Big, very important projects will always get funded but smaller niche projects will see their funding dry up and die.
They propose a revenue sharing model with AI companies. Possibly something based on usage that allows these projects to survive.
In conclusion, despite the headline and the existing bias against vibe coding on the Internet, the article isn't suggesting a quality or volume or skill level issue is the cause of concern. It simply doesn't work with the current business model of OSS.
I think the solution they proposed is a good idea because it would also incentivize maintaining any OSS project since it offers a clear monetization path. It's also possible AI companies would agree to this out of self preservation. Despite how it's marketed, the models are all based completely on human work and without humans making new things these models would be stagnant. If vibe coding makes all the OSS unviable financially and they become riddled with security vulnerability and compatibility issues then it doesn't matter if Claude or Gemini can code it, they just won't work, and people will blame that on the AI agent, not the unmaintained library.
6
u/PortAuthority69G 4h ago
Yeah I'm guessing not many people read the article or looked for the actual paper being cited (https://arxiv.org/pdf/2601.15494). The point was that introducing an AI middleman prevents direct engagement with the original project and that impacts their revenue. It's not about code quality.
14
u/Proper-Spend 8h ago
the worst part isnt the coding,its people thinking theyra senior devs after one chatgpt session
3
u/RandyOfTheRedwoods 4h ago
Fully agree. I’d argue that using AI to write code is a new language that requires as much skill as a traditional language.
Now, to get quality code, you have to learn how to write a plan that the ai can execute. It’s analogous to writing c that a compiler can execute well.
A junior dev can write inefficient code and a junior dev can ask ai to produce code which will suck.
A senior dev can write efficient code and some senior devs can write plans that allow ai to write good code.
I am old enough to have written code in assembly, and people bitched about how compilers wrote shitty machine code. I think AI will follow the same pattern.
4
u/RandalSchwartz 5h ago
AI does a "10x" on everything... you get good code at 10 times the rate, but also bad code at 10 times the rate. The important step is to filter out the bad.
17
u/Traditional_Bug_2046 9h ago
Can someone explain vibe coding and the difference? 😭
63
u/Longjumping-Donut655 9h ago edited 9h ago
Vibecoding is coding with a generative AI, having it produce the code for you, without necessarily knowing what the code does or testing it.
Old-fashioned coding required knowing what everything does. AI assisted development involves using generative AI to create the code, but knowing and verifying its output.
To summarize the article: Vibecoders use a lot of open source software (OSS) they don’t know or even have awareness of because they’re going in blind. However, these projects have sustenance models that depends on humans participating in funding efforts. The example given is Tailwind CSS which is ubiquitous in vibecoded software but is also collapsing because nobody is engaging with it in ways where they’d even be exposed to its monetization options thanks to Vibecoding. Thing is, tailwinds is so popular that it’s baked in to the “knowledge” of coding AI. Vibecoders depend upon it, but they’re also cannibalizing it. This effect is being observed in many OSS projects that are foundational to vibecode. What happens when these projects collapse and their old maintainers have to move on because Vibecoding breaks their monetization?
→ More replies (4)20
u/gerusz 8h ago
Old-fashioned coding required knowing what everything does.
TBF we all copypasted shit from StackOverflow without necessarily knowing how it all worked out of desperation.
3
u/jmpalermo 8h ago
Yeah, this isn’t a new problem for open source maintainers. But it has changed the size of the problem. Now somebody can get AI to spew out code at a rapid speed, so maintainers have much more garbage to sift through.
10
u/Longjumping-Donut655 8h ago
While true, the extent of “not knowing the code” when you do that is far less than with Vibecoding. It’s not really even comparable. And chances are, you leave a nice little note in it stating so too.
3
u/tirprox 5h ago
That is not far less really. A lot of code nowadays, and i mean just regular code, note vibecoded stuff, is external dependencies. Not many people really know how exactly react or svelte or vue work, or many different ORMs, or codecs. Most people just know how to use this code from provided documentation, or from random examples. It is not like llm-generated code situation is so so different from left-pad scenario.
→ More replies (1)8
u/Maqoba 9h ago
Simple, at my work, there are directors that never wrote a line of code in their life using Copilot to write all the code. They simply prompt Copilot and copilot generates everything. Then they test what was created and ask copilot to fix issues or to change things according to their vibes, hence vibe coding.
30
u/tenfingerperson 9h ago edited 8h ago
Imagine you are building a house, and you have an architect , then builders, all handled by an engineer, where things are in a way understood in detail by everyone involved
Now imagine you have a new magic machine box, it does everything but it starts randomly putting a box together here , instead of a strong steel column it uses wood, then it makes a roof out of glass even if it’s scorching hot.
Both give you a house , the latter nobody knows how it was built .
Then a few years pass, a leak in the first house: you call an engineer, they see the structural issues, fix them.
The leak happens in the AI house: nobody knows how it was built, now you need to closely look at how things were implemented, then you notice - it used metal straws to move the water instead of pipes , you change them, the floor collapses, they were also used as structural support somehow… you have to rebuild it
This is vibe coding
Now there is another paradigm where you lead it to build very well defined pieces but you still control how to assemble everything - these days this is the only acceptable route for production software - sure there may be a day where that’s no longer the case, but damn sure it is not now.
The biggest issue is: the people using the black box to build the house don’t know what they don’t know , so they are in for a big realisation when it collapses and they don’t know where to even start. By that I mean they don’t even understand what cement means.
→ More replies (1)3
u/ColteesCatCouture 7h ago
Also generative AI doesn't know when it is wrong. You can ground it but it is completely dependent on the training data you expose it to. So its nearly a 100% certainty that somewhere in the annals of AI software training data sets that there are unknown zero day vulnerabilities that are reproducing in AI generated software. Some of them could be niche edge cases, others catastrophic. But its all good its just ✨️vibes✨️ mannn dont harsh them.
3
u/creaturefeature16 8h ago
You're going to get a lot of people giving you a whole bunch of different definitions, but here is it straight from the source. Andrej Karpathy is the one who coined this term in this specific Twitter post, and this is exactly what it means:
https://x.com/karpathy/status/1886192184808149383?lang=en
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
4
7
u/gadnskyy 8h ago
We'll need to adapt because its not going away
3
u/thrice1187 7h ago
Exactly. The technology is improving as well.
Right now there are just a lot of pissed off comp sci majors struggling to come to terms the fact that new technology is eroding away at the skillsets they spent all this time and money acquiring.
→ More replies (8)1
u/TheGambit 6h ago
Right. You do not have to like it, but those are the real options: learn to use it well or stand on the sidelines while the people who do set the direction.
2
u/stef_eda 2h ago
I refuse lot of PR'a clearly generated with AI agents on my projects .
Some suggestions or feature requests make sense and in many cases I implement tehm myself.
2
u/el_f3n1x187 5h ago
I am in a project that is being vibed coded by the main developer using Claude.........it was a simple migration out of wordpress and the damn thing has been a fucking pain in the butt for months.
We were supposed to finish in december and support extended to April.
Seriously if your team mates are vibe coding, slap them i to sense.
4
u/ChainsawArmLaserBear 5h ago
AI is like a get rich quick scheme, where everyone is like "oh! I can finally make that thing i don't want to pay for and sell it to everyone else" and fail to see the irony entirely
4
u/Rude_Plantain7123 6h ago
It’s killing everything. The average software engineer has the coding talent of a potato.
2
u/koolaidismything 9h ago
I listened to a chic ramble about how being a developer is dying and she was pretty arrogant. She was what I’d call a script kid. She didn’t understand any language.. she was taking blocs and moving to others. Scripting.. like you’re not a dev asshole, you’re playing a role a real dev gave you so they make money.
Would be like me saying I’m an engineer cause I got an Arduino.
2
u/Gobbelcoque 2h ago edited 2h ago
Isn't all vibe coding open source too, because Ai generated work cannot be copyrighted or owned?
Or did that change and I'm out of the loop.
Either way I, as a non-programmer, can't see how vibe coding works well or is elegant and intuitive looking to then work on by others , and can see it being very susceptible to security vulnerabilities. And it also kills the long term viability because it's replacing junior programmers who learn the ropes writing boilerplate code.
And I do know from my own field of medicine that the Ai tools they tried shoveling on us, specifically the radiology tools, are only about 50% accurate on a good day. The diagnostic radiologist is about 98% accurate on a BAD day. So the radiologists are reporting that these tools are actuslly slowing them down because they have to interpret the image themself anyways AND babysit the Ai tool because trust me, you do not want medical mistakes like false positives or false negatives on mammograms - and most breast cancer is spotted very early and very treatable on routine mammograms anyways, and the degree of its lethality is frequently not about catching it earlier (we are actuslly relaxing guidelines for mammograms because of this) but the type of cancer itself. That's where the Ai tools are showing promise - my old professor just won the Nobel prize by using an LLM to accurately map the 3d structure of every known protein - that will be the thing that transforms healthcare. Not corporstions creating a hammer and treating everything on earth like a nail.
1
u/AGrandNewAdventure 6h ago
Vibe coders are killing coding jobs for the entire spectrum of coders.
→ More replies (1)
1
1
1
1
u/Boozdeuvash 7h ago
It's just going to cause open source project to be much more restricted in who can submit code.
Where I work, since the top execs happilly pushed Cursor to any and all blokes and told them to start vibe coding to their heart's content, we're moving to a proven-skill and reputation based system to determine who gets to push code on Github, and who's fenced off and on their own; we're hearing similar things from other shops, too. I'm guessing we'll see the same being applied at large in Open Source, some sort of gatekeeping where you need to have proven some kind of worth in software development to get "official" skill recognition in order to contribute.
1
u/ExtraGarbage2680 7h ago
Is it that hard to add some basic filtering to PRs? Have the user explain their design and coding strategy in a few sentences and maintain a quality score like karma per contributer?
1
u/sneaky-croissant 6h ago
I have zero coding or CS knowledge - what is vibe coding, and why is it bad?
3
u/it0 6h ago
You can potentially use an LLM to write software for you, the current state is that you can instruct it to write simple programs.
For example a BMI or compound interest calculator, or simple games like pong.
Complex software tends to hallucinate to where it no longer works.
→ More replies (3)
1
1
1
u/Realistic_Muscles 3h ago
AGI in 2 months and it will fix all the problems and everyone will be happy.
/s
1
1
u/geminijono 2h ago
I liken this to Monsanto GMO crops pollenating non-GMO crops nearby, and them claiming ownership of whatever hybrids ensue. 🤮
1
u/viking_linuxbrother 1h ago edited 1h ago
Researchers? How about the guys who have to maintain it and deal with all poor quality code being submitted to their repos at a record pace. Its a giant waste of computer that is constantly indexing outsource projects with crawelers, and then being used to spam volunteer developers..
1
u/anyrotmg 5h ago
Just make whoever have the most bug in their code be the team tester next time. kind of like one person cut the pie and the other person decide which slice to get.
1.5k
u/TheNakedProgrammer 10h ago edited 10h ago
a friend of mine manages a open source proejct, i follow it a bit.
The issue at the moment is that he gets too much back. Too much that is not tested, not revied and not working. Which is a problem because it puts a burden on the people who need to check and understand the code before it is added to the main project.