vibe-coding, your thoughts?

Vibe coding, just like all AI generated coding, is done by people who don't really love coding, and in most cases people who don't truly understand what the AI is producing.

Reading code might sound easy at the surface but is actually the hardest part of coding, as it requires engaging with someone else's train of thought. It's easy to be convinced about the logical soundness of something if we aren't deeply involved in researching that thing, just like it's easy to be swayed by populist propaganda if we take everything at face value, because there are a number of caveats that, without involvement, we can simply not be aware of, so the first line of defense when it comes to quality and safety in software are the developers who write the code themselves, and that line of defense simply doesn't exist if the code is AI-generated. Furthermore, anyone who isn't skilled enough to implement a solution themselves is also totally incompetent to review other people's implementations, and that includes AI-generated code.

Even if AI was really good at coding and truly raised the ceiling, as is apparently the case with theoretical math, there would still be fundamental problems like token costs currently being heavily subsidized, the impact of data centers and their cooling needs in nature, the the economic inequalities, and the general dumbing down of human intelligence. I mean what would our purpose be in a world full of machines individually more intelligent than us? Do we really want that future? I certainly don't, I value humans and their creativity way too much to let go that easily, so I'll never let anyone including AI prevent me from learning and gaining experience. Each time we outsource the solutions to our problems is a lost opportunity to learn.

At the end of the day, I just want a tool that actually works. Call it vibecoding or whatever else you want—AI is everywhere now, and I get why people freak out about code breaking. But honestly? Give me software that solves a real problem, and I couldn't care less who built it.

Without getting into the debate, here's something useful from Devin Prater on Mastodon (@[email protected]).

Blind Vibe Coding

A screen-reader-friendly directory of resources for blind and low vision people who use a screen reader and build apps with help from AI.

This directory lists English-language resources for blind and low vision people who use a screen reader and want to build apps with help from AI, sometimes called “vibe coding.” It covers guides, tools, courses, communities, podcasts, articles, and research, free and paid, for Windows, Mac, iOS, Android, Linux, and the web. Every resource explicitly mentions blindness, screen readers, or accessibility. Every resource was published or updated in 2024 or later, and every link was checked on 1 October 2026.

https://jamalmazrui.github.io/BlindVibeCoding/

Agree with maldalin and others, enough said.
Its worth noting that so what if someone vibe codes? Obviously you have to try and do your best. In order to avoid mess ups. But the opposite is also true, plenty of codersAbsolutely suck at it. Plenty of coders probably right terrible code. Like with anything else in life, there are people who are incompetent at their job, lazy, they don’t put the effort, it’s not a matter of, oh if you don’t bother learning reading code, etc, or Coding You Love it. no, I asure you, there's plenty of people who just code because, it’s a job, and nothing else. They don’t necessarily love it. They might actually hate it for all one knows, and in any case if they love it or not doesn't matter, since it pays the bills? You get the point. now. Does having coding knowledge, etc Help? Yeah, no shit, it makes things easier. But saying that oh vibecoding isn't loving coding, not how life works, but I digress. In the end, one can only do their best at what they're doing, that's about it. Not to mention the obvious... There is way more to coding than just reading and writing code. You could be the best programmer / coder in the world, but if you don’t have the proper ideas of what you want to code, how to make it i.e as far as logic, ideas to bring the architecture to life so to speak, what do you need to do to make it happen, you could be the greatest coder in the world, and you’re application, software, what have you, could still turn out to be absolute garbage. Just look at an example of all accessibility problems of say, meta? All the accessibility regressions? or insert name of software that has terrible ui or ux?point made. That software was coded more than likely by people. Point is, its not just coding, coding is a branch of a much, much bigger tree, if you will. Anyway, those are my thoughts.
As far as the child labor stuff? First? Completely out of topic. Second? Absolutely nothing to do With the current discussion. Thirdly? You cannot do anything about it. Suppose you stop buying from a company that you know uses child labor. Guess what? There are likely dozens more companies who use child laber. Whether you choose to not buy from one, yeah, good luck, you’re likely buying things from 10 other companies that also use child labor. You cannot do squat to stop it, or change it. Also? Funny, well ironic that you mentioned child labor. Why? Guess which company has used child laber? in the passed? Weather they still do or don't doesn't matter; they have done so in the passed.
Apple.
https://humantraffickingsearch.org/resource/new-forced-labor-and-child-labor-charges-for-tech-giant-apple/
That is just one link. I can pull up more, and of more companies besides. What I’m going towards, is that was rich. Coming from you, someone who owns multipleapple devices? using your logic? You bought a Apple device? Congratulations, you're supporting Child labor...
I myself of course don’t go for that philosophy, I think it’s bullshit, and it’s way too black and white, but enough said.

Okay, let's get away from child labor and back to vibecoding, please... Thanks 😊

Hi all,
I vibe code a lot. I actually released one thing, a static HTML page with a list of resources as part of the mailing list I run. I tested it extensively before releasing it, and I know a bit about accessible web development which helps, so I was able to tell Codex from ChatGPT how I wanted the site to be designed. It took me a few hours to test and debug but it was worth it. I still add things to it from time to time. Another significant thing I tried to do: I uploaded a pull request to a developer on Github, because according to some people on Mastodon it had some security holes. And when I took steps to reproduce said security issues they were there. So I got the code from Github, put it through Codex, and asked it to suggest ways of improving the security, and I got it to look at another NVDA add-on from a developer I know who implements good security for his add-ons. Said developer can actually code by hand, but he can code from scratch so he knows what he's talking about. In short, I did a bit of research into Windows DPAPI, told the add-on to implement things, and then I tested it to make sure security issues had gone away. The issue was the API keys were being saved in NVDA's ini.txt file and in some log files too. But the fix I vibe coded meant that Windows DPAPI was being used to hide API keys, and they weren't being saved in NVDA .ini files. I tested this and it did actually work. So, I had a security fix, but my PR got rejected. The developer gave me a lot of feedback as to why, which actually helped. He didn't merge the PR I submitted. But I later implemented the improvements he suggested and now use my fork as opposed to the original. One of the reasons it got rejected was because Codex hadn't first implemented the security everywhere like I'd thought. Keys were still being exposed in NVDA's log file under certain circumstances. It got to the stage that I hadn't remembered what I'd tessted and hadn't tested, but either way, that slipped through. So the disadvantage of vibe coding is it can miss some security implementation. It might suggest security fixes, but it doesn't necessarily implement them across the board, it only partially implements them. This is where vibe coding really falls short. It's the sort of thing where a developer has to know all the possible scenarios a vibe coded security implementation might miss. I've tried vibe coding a few NVDA add-ons, but never finished them, because if you want something without bugs you really need to test for hours. I vibe coded myself an iOS app for listening to the radio with an interface and features I want, but I certainly won't be paying for an Apple developer account to release it, and it's far too buggy to be released anyway. It's got bugs that annoy even me. Vibe coding isn't a problem at all, provided you test your software extensively before releasing or giving your code to others to work on. The reason some developers seem to hate vibe coding is because they're given vibe coded stuff by colleagues to work on, but because they've just stuck it through an LLM with no testing.