We all know that the programmers are using AI tools to complement their work, but the city has a new trend that takes things to the next level. The term “vibe coding” was coined by OpenAII co-founder Andrez Karpathi last month, but what started as a random X post has quickly split into a new community.
What Karpathi has described in his post is making software without writing any code – whatever he does, he explains what he wants for his AI tool and it accepts all the output. Even he uses a dictation tool to avoid using his keyboard. Looks crazy, don’t you? This is because it is.
What is really vibe coding?
Most AI coding equipment now do three things:
- Create auto-perfect suggestions when typing a line of user code
- Explain, summarize, debug, or advise you on the codes you provided
- Create fragmentation of code based on your natural language signals
They are designed to help those who know how to code – with some studies and focus on education. Even cursor, one of the main devices, is currently using the vibe code, actually designed for developers. This is to speed up simple processes for those who would be coding whether the equipment was present or not.
For example, take this random feature explanation from the cursor website: “Cursor lets you write the code using the instructions. Update the entire classrooms or tasks with a simple prompt.” Certainly, the purpose of the convenience is to save you from writing the code manually – but you still have to know that things like classes and functions are for good use of it.
Vibi coding (or vibe coding is quickly what is happening) is a trend where people take these devices and try to make something with low software development knowledge – simply describe the results in natural language that they want to see as a final user.
Why is vibe coding problematic for your users?
When a completely non-technical person opens a cursor and starts vibe coding, the results will be very different since a person such as a movement like a movement. Where Karpathi can “ask the cursor to generate some codes that the user has a hash and saline password for authentication,” can call a non-technical vibe kodar “O Cursor, create a safe database to store my password.”
Certainly, they used the word “safe” – but it is exactly the same kind of expansion that can ignore an LLM randomly. Alternatively, its idea of ”secure” may not even have commercial software standards, or it may add safety measures in some places and not others. There is another problem with this phraising, also – “Store my password” part. It is very common to think about the password because it is being “stored” somewhere, but if you know what passwords are salty and haveing, you know that users’ passwords are not technically stored anywhere.
Instead, the hash value of salt and consent salt and password is stored – and despite all crazy words in that sentence, it is not a complex concept. However, this is something that you will never know until you went out in a purposeful manner and learned about it. And if you do not know it, you cannot ask for it.
So, instead, you have requested a safe database – but which version of LLM genie will be found? The one who takes your prompt literally and stores the password as in a random small database? Or what he believes that what you really want to achieve and comes with a proper certification process for you?
I think the most accurate answer is that sometimes you find medium-centered genie, sometimes you will find another time of one kind, and a lot of time, you will find something in the middle-there is no real poem or reason for this. It can work 100%, it can 90%, it can do 5%. With an indication that something can be unclear, anything, and the problem is-there is no way to understand or decide the result of a non-technical vibe coder or to decide how good it is.
You cannot even write proper tests to find out what is going on if you do not know what safety measures you need, what you do, what they should achieve, or what success and failure can be seen.
After all, you will not be implemented in your software, bad, broken, or breaking zero safety measures. It may still seem that it is doing everything correctly at the end of the user – but behind the closed doors, your users’ sensitive information (personal data, payment information, use history) will be fully ready to steal unsecured and bad actors. And it is bad for you as well as for your customers – the cause of safety violations is nothing but stress, scam and financial loss for product owners.
When Curpeethi described her vibe coding experiments, she said that he and the cursor “do most of the work,” the code produces, and I am not here to claim that “mostly works” is unacceptable. There are always all kinds of problems hidden in every code base for every product. These days with software size and complexity, it is only unavoidable.
But if you want to release your project to the public and charge people to use it – then you have a responsibility to make it as safe as you can. Except for sensitive information, unprotected information is not good – and assuming that it is preserved without confirming it properly.
If you need a real-life caution story- @ @ leojr94 on x on x everything you need. Here his story is condensed in three x posts:
Why is Vibe coding problematic for you?
Software is expensive. Even if you cut all development costs through vibe coding, you will still have to pay to store your data, send it around between yourself and your users, and interact with other services via API.
The services you use for this, such as AWS, are usually paid-like-to-go, which means that you only pay what you need. It’s great, isn’t it? Sure. But when you are not under the control of the software you are developing, you are not under the control of data usage. Your code, produced in random division and splitted together, is likely to be extremely disable. Just some badly designed lines can produce 3x, 5x, or even 10x more data, which you really need – and sending that unnecessary data between you and your users will cost you a lot of extra money. The most explosive way can be wrong when things go right.
Imagine that you have some users, you have some bills, growth is slow but stable, and you can deal with it. But one day you wake up and your social media content has gone viral, running thousands of people in your software product. This will be great, except for the fact that your AWS bill is too large and you note that the cost of your network traffic per user is actually more than the membership cost they are paying you.
What is the solution?
At this point, some people will start suggest more products. Platforms designed for vibe coders and “non-technicals” that provide additional assistance to users for safety, servers and other backand goods. Some people may also say that with some twicex, vibe coding may be just what software development needs to be shut down for becoming democratic and exclusion.
I have a different opinion – it is already democratic and it is already inclusive (although I don’t think it is a word). Anywhere any computer can learn about science, coding, programming, or software development until they have an computer and an internet connection – and it is what people do. A large number of programmers are self-reliant and they probably will always be. You have everything you need, which leads me to the “rigid truth” of the situation: if you want to make software, hard luck – you need to learn how to do it.
If you have an idea, you are either attempting to know how to make it or you can help in finding those partners and investors who can help bring it to life. There is no grift, a zero-ex-opt, where you magically finish with a working product in a negligible amount and you have no partner with which you need to share the benefits. It is not how the world works, and it is not how it should work, either.
If you want to speak another language, then you have to learn it. If you want to play the guitar, then you have to learn how. And if you want to make software – then you have to learn to make software. If you like the DIY path, very good news – Any person is also a means of seating and studying programming using free or paid courses to vibrate the code using free or free or paid software. You may also use AI tool to speed up things.
And I’m not joking when I say anyone can do this – programming is actually so big that even the “type of programming” is available to all. Certainly, not every person will become a software architect in a top company – but some people will learn enough to make games in C ++, other people will learn enough to create an app with python, and even if you decide that coding is not really your point, you will probably still be able to create a website with HTML. Whether you are a professional study bug or you have never studied in your life, and whether you’re a mathematics whites or you are terrible with numbers – you will be able to make something.
How long will there be a stick around the vibe coding?
Now, it is impossible to know what Karpathi achieved by running this small experiment or posting it online. For me, the X post reads in this way: “Man, this AI stuff is going crazy. I can deliberately take bad decisions, deliberately ask for dumb things, and somehow I do something that still works.”
Other people have explained it more like “Wow, you can make software, even if you do not understand how to code.” No. Big nope. You cannot do this. You may think that the obstacle between you and you applied is that cryptic nonsense programmers sit and type all day – that you can’t make anything because you don’t know how to type how to type how to type code,
But this is not. You can start understanding all the stuff that is studying it only after a few hours. This is just the language, the method of communication between you and the computer, and it is in importance compared to real information you want to communicate. If your goal in life is to have a deep and completely technical interaction with a Spanish experimental physicist in your native language – then you will not get it only by learning Spanish.
Software design, understanding algorithm, managing data, meeting safety standards, construction for scale, adaptation and debugging – these are skills that create software. So it does not matter that the cursor lets you avoid typing code, if you do not know anything about the apps, you can still not create an appropriate app.
I really do not know how much vibe coding will be found or how long it will last, but I don’t think it is worth it for a non-technical person and is ready to code a product. I do not even think that trying a vib-coded product is worth the risk for consumers-there is no way to know whether your password and payment information is safe or not. If you see a newly developed product in which you are interested – consider knowing who made it and how it was made before you give them money.
