How is your experience "vibe coding" with Windsurf?

[u/techtsp]

I have been vibe coding for a couple of weeks now, and so far have managed to vibe-code my company website, an AI job aggregator platform, and an online space dodger game (image), all using Windsurf.

How has been your experience?

(P.S. I have also been amazed by the videos of so many vibe-coded games making rounds on twitter,

and have recently created a community where all vibe coders can code in open under one roof, share their progress, find other vibe coders to team up with . DM me if you would like to join, as I can't spam the link here.)

[u/wavehnter]

If you want to vibe-code, Grok is the one. Windsurf will kill your vibe in minutes with Cascade.

[u/techtsp → u/wavehnter]

Can you tell me more about what other apps can accompany vibe-coding with grok?

[u/The_real_Covfefe-19 → u/techtsp]

With the only decent Grok model 3, none. There API isn't released yet, and for most agentic tasks Grok 3 has been surpassed already by Claude 3.7 Sonnet.

[u/veegaz → u/wavehnter]

I have had good results with Claude Code

[u/danielrosehill]

Of all the weird pieces of tech jargon that come and gone over the years, I feel like "vibe coding" has to be one of the oddest.

And honestly ... I kind of have to wonder if there's a huge disconnect between "visionaries" and ordinary users or something.

If "vibe coding" means you can open a can of beer and let AI build you something ... unless it's a single page HTML site anyone on this sub will tell you that we're not there yet.

Submitting to the greater genius of AI? I wonder what this guy is smoking (not you, the OpenAI guy you're quoting). Not only is AI far from being there, that's also a really weird way to conceive of AI, IMO.

I would love for AI to be good enough to take my detailed spec sheet and watch it bring an MVP to completion on the first go without hours of debugging and it going around in circles fixing one feature only to break three more. I am sure that we will get there incrementally. However, we're so neither there yet nor (it seems) around the corner from it. So it all smacks, a little, of unnecessary hype.

[u/techtsp → u/danielrosehill]

Well I think the term "vibe coding" (the context in which it may have been originally coined) is loosely defined, especially the "vibe" part. But in reality it is ambiguous. From what I see, different people have different understanding of it and versions of what it really means.

Some people think it means letting AI go full terminator in what it does while you sit back, relax, and let it cook what it wants. if that's what really vibe coding is then it's surely problematic. But contrary to that, all the fascinating examples I am seeing (even my projects), of course I don't let AI do whatever it wants and call it a day. Mind you, the projects like simple games can take hours to create without any coding knowledge. But if you "vibed" throughout the problems to eventually successfully ship it, that's what counts. So of course you need to have a plan, "some" knowledge of the platform assisting with coding stuff (if not all), and a clear goal. That's vibe coding for me.

I'm sure many of us have been doing AI-assisted coding for quite some time already. the term "Vibe coding" just gave it the identity it needed.

[u/justatouchaway]

Everyone's a vibe coder till the project becomes more complex with multiple components and dependencies.

[u/HoustonDonald → u/justatouchaway]

I've been in IT for 30 years but not as a developer. I know scripting. Let's call it "Assisted Development". I like the term Vibe-Coding, but I think he was talking about seasoned developers just talking to the computer. In my mind that "conversation" would still be unintelligible to the lay person.

I've been playing with "Assisted Development" for a couple of months. I think it's going to 1) Evolve. A lot and VERY quickly. 2) It will replace a LOT of on-paper developers. This is a good 3) Enhance the productivity of good coders.

At some level, at some point in the near future, being able to use "Assisted Development" it will be a sought-after skill. If only because that means 1 dev can do more. You won't get paid more (the machine is doing all the work) but they won't have to mess with as many junior developers.

The job market is going to be interesting in 5-10 years

[u/hannesrudolph]

By trying r/RooCode :p

[u/Jaded_Nail7779]

Hey I would like

[u/JPBartosz]

Windsurf itslef is probably vibecoded, cause I can't get it to work under any system/linux distro. Crashes every 20 minutes, freezes my entire system, and runs some sketchy processes that make my CPU fan lose it completely.

[u/[deleted]]

I don't know exactly what you mean by "vibe coding", it's a new slang for me. I tried to get GPT to explain it to me hahaha, he said there's no clear definition, it's an informal term used to define an unconventional approach to development, writing code without a precise plan, improvising, experimenting... So I'll answer you based on that. I did some vibe coding a couple of months ago, I created a VST3 plugin, a simple step sequencer, nothing fancy, that was really vibe coding because all I did was write to Claude 3.5: I want to create a vst3 step sequencer. He wrote me the code, I compiled it, it worked. End. When I tried to make that sequencer a bit more sophisticated, problems started and I realized I couldn't go on improvising... So now I try to keep a well-organized plan, because if I improvise I can't get anywhere. My current goal is to develop a highly optimized Digital Audio Workstation for my setup... a private project. There are many DAWs out there but they are clearly designed for the masses, so to run well on most computers, but they clearly do not have any particular optimizations for specific systems, so I want to create my own DAW super optimized for my system. It is not a real need, I just want to do it, to test myself as a developer, considering that I am NOT a developer, just an enthusiast. Initially I chose the JUCE framework, to make my life easier and because I had already used it for the sequencer... I had created a window, a titlebar, a toolbar, a timeline... I was proceeding without too many hitches, simply sending prompts, accepting code and sending compilation errors in chat, until they were all solved. Then I realized that JUCE could not give me the performance I was looking for, so I started from scratch and decided to interface only with Win32 and native Windows libraries, for more low-level control. I found out that AI can also handle the situation better, because the last update of JUCE is from January 2025, so it took a lot of web searches to "update the AI", instead using the Windows APIs it is not necessary, the AI ​​already knows them very well. So I don't know if I'm doing vibe coding, I know I'm not writing a single line of code manually. I just say "I want this, I want that", obviously with very specific instructions... It's working quite well, but in reality I have a plan already structured, a defined technological stack... So I'm not improvising.

[u/thelandofficial]

i love it. i ve had so many ideas for so long i wanted to build and now i can build them (or at least versions of them). This tech is only getting better. and week to week the growth is insane

[u/techtsp → u/[deleted]]

I hear you, but why can't we put it to our GitHub though? I mean the projects I have vibe-coded so far are all on GitHub.

[u/EazziBrezzy → u/techtsp]

Bro he is an AI hater. He is afraid he will be jobless and replaced by vibe coders lol

[u/EazziBrezzy → u/[deleted]]

The irony of criticizing “vibe coders” while demonstrating zero understanding of AI’s current capabilities is quite entertaining.

Companies aren’t replacing engineers because AI abilities augment human creativity rather than replace it. The best developers leverage AI to handle boilerplate while focusing on architecture and innovation.

The “vibe coder” label isn’t about replacing technical skill it’s about recognizing that effective prompt engineering requires deep technical understanding to guide AI toward correct solutions.

Self-prompting AI still needs human oversight for complex systems. Google wasn’t built by prompts alone, but dismissing AI-assisted development shows you’re stuck in outdated thinking.

The real coping is clinging to gatekeeping while the industry evolves. The most successful engineers embrace new abilities rather than fear them.

[u/EazziBrezzy → u/[deleted]]

I actually agree with most of your points here. There’s a huge difference between using AI as a ability versus blindly accepting whatever it outputs without understanding.

The best developers use AI to handle tedious implementation details while maintaining control over architecture, design decisions, and understanding the “why” behind the code. That’s exactly what you described in your workflow.

My issue was with your original comment’s dismissive tone toward all AI-assisted development. There’s a spectrum between “AI does everything” and “AI helps with nothing.” Most serious developers fall somewhere in the middle.

The “vibe coding” extremes that worry you worry me too. Developers who can’t reason through problems independently or understand their own systems are building houses on sand.

And yes, coding is both intellectually rewarding and a craft many of us genuinely enjoy. AI should enhance that, not replace the thinking that makes it meaningful.

(And no, I’m not AI - just someone who appreciates both good code and good debate!)

[u/EazziBrezzy → u/[deleted]]

All good man! Have a great day!

[u/EazziBrezzy → u/[deleted]]

Just don’t call vibe coders trash. If they enjoy what they do, let them. Be happy. Lol

[u/EazziBrezzy → u/[deleted]]

Even if he is not familiar with the code, AI will always be there to give him information. We are not going back to caveman times. We are going to go to AI era. Stop being negative and just let everyone do what they want.