I just vibe-coded a Netflix-styled Portfolio with all my products that I built over the period as an Indiehacker and Product-manager and vibe-coder.

Link to portfolio: https://sushilnarayanan.com/

Today, traditional engineering interviews often revolve around DSA (Data Structures and Algorithms).
And while DSA tests analytical rigor, it also wires thinking into strict, logical frames.

Creativity lives outside those frames.
Problem-solving and creating experiences are two entirely different games.
And sometimes, forcing a purely analytical mindset can quietly erode creative instincts the very instincts vibe coders thrive on.

Which raises a bigger question:

Is the future of technology moving into the hands of more imaginative, creative builders rather than traditional analytical problem-solvers?

I'm super curious how everyone starts to vibe code? In the beginning I would simply jump into @bolt.new or @Cursor and just do a prompt and continue refining with the AI. I quickly realized this created a lot of issues as I didn't think about the structure, tech stack, and how I wanted the features to interact with each other and how the way I was building things would impact the user experience. I now do the following:

• Write down a simple problem statement: "what am I trying to solve?"

• Write down a simple solution statement: "what does the thing I'm building do (to solve the problem)"

• Share the above with @ChatGPT by OpenAI and word vomit my thoughts, ideas, how I want the user to interact with my app, etc and ASK ChatGPT to turn everything I said and want into an easy to understand directive and instructions for an Engineer.

• I then take the Engineer instructions and give it to a new chat in ChatGPT and ask it to turn those instructions into a prompt for an AI engineer and to break up the project into sections so that each time we focus on a section the app is shippable and keeps things easy to work on.

• I take the output and paste it into my notes. I then give it to Cursor.

• Once in Cursor, I create a new project folder and got at it!

Curious what everyone else does and if you've experience any things to avoid or must do

Live Feb 28th, 9am PT - drop your questions!

Hi everyone,
CEO of Bolt here! Super excited to open up about our journey and offer any learnings and stories I can to help other makers on their journey. Within a span of 2 months we've grown to $20M in revenue and were recently featured in NYT as paving the way for vibe coding.

I've been vibe coding for a few months as a non-coder and I'm still annoyed with the fact that I can't understand what's happening under the hood.

I've got a decent understanding of code but I can't actually write it and I don't know the best practices for stuff like architecture and security which apparently aren't baked into most vibe coding tools. So my question is...

Hey p/bolt-new community,

I recently started building Couples Hub (https://coupleshub.io/) a React-based application and Next.js based landing page using Bolt.new. Couples Hub is a product of my hobby brand "MD Meets Techie" which I've run for the past four years, creating digital products specifically for couples. Given my technical background, diving into Bolt.new was kind of a fun experiment (esp given how drab and boring my day job is). I noted several challenges along the way and I thought I'll share a few tips on what I've learned thus far. 

On October 31, 2024, my entire world crashed. My developer left, and with that, so did my sense of control. It felt like someone had yanked the engine out of a speeding car, leaving me skidding on an empty highway with no brakes.

Is it truly vibe coding if there aren't tunes making the vibes...well...vibey. Thought it'd be fun to put together a YouTube playlist of what everyone listens to when building! I'll take all the links and make a playlist on YouTube after a couple of days :)
Just drop the link and tag the tool that you mostly use. I'll start!
I vibe with Black Coffee and mostly use @Cursor!

For Valentine's day I used @Replit to make an app (PWA) that lets me and my partner "hug" via notifications, and has an exploding heart when we're both touching a button at the same time.

What I'm stoked on:
I was able to get a prototype in minutes even though it had a lot of flaws. It took me a couple of sessions over a few days to build an app that kind of works. This was pretty mind-blowing, as my coding ability is fairly rudimentary (background in data science and I've done some basic javascript but never built a standalone app).
Using @Wispr Flow sped things up and also was impressive - It's cool to see the little touches that Wispr has implemented to improve dictation, and I'm just impressed by the speed and fluidity of using it on desktop. As a side note, using Wispr has made me increasingly frustrated at how poor iOS's built-in voice dictation is.
What I'm frustrated by:
I had to restart building the app a couple times because when I would try to get it to fix certain things, it would create more problems. It felt like working with a very fast but extremely inexperienced developer who has no sense of when they're off on a dead-end in the maze.
I haven't developed an intuition on when to use agent and when to use assistant. Replit shows how the agent is more expensive than the assistant, which stressed me out a bit. Although I realized I never hit the threshold where it started charging me more than my normal subscription. So I think it was just a psychological thing.
It had repeated errors around web socket connections and dealing with notifications on iOS. I had to get deeper and deeper into these myself, and in one case, teach it how to do notifications properly on iOS. It turned out that Replit's information was outdated, and it thought that it is not possible to do native notifications with a PWA on iOS. So I had to actually get code from ChatGPT to teach it.
It was stressful to make a change knowing that I could break and was likely to break many other things, and I didn't know how to properly create a checkpoint that I could fall back to. It creates checkpoints all the time, but I couldn't figure out how to name a checkpoint or save it in a way that was easily recoverable.
Because it takes some time for Replit to compile, I've found myself doing other things like work, little tasks, or even watching a TV show while waiting for Replit. But then I had to keep checking because it wouldn't send me a notification. I wonder if there's a way to send notifications?
Help me make my workflow better! What am I doing wrong / what could I be doing that I'm not doing?

4 days ago Tom Blomfield from Y Combinator posted a video explaining some of the techniques to be good at Vibe Coding. Tom says in the start that the best techniques for Vibe Coding are the ones used by professional Software Engineers to write code (kinda ironic).
Before we talk about what Tom has to say about Vibe Coding, here are some of the reviews about Vibe Coding from the YC Founders.
Nicole Lu - If your AI editor is taking you into a loop, sometimes it helps to go to the LLM's website and paste the same code.
Skyler Ji - I open both Cursor and Windsurf side by side, give them the same problem to solve and pick the best response.
Sacha Servan-Schreiber - Take Vibe Coding as a new programming language. And to get the best results, you will have to provide a lot of context
Arshad Shaikh - I usually do Vibe Coding in the reverse direction. I write the test cases followed by the code that then has to satisfy these test cases. I never micro-manage an LLM while Vibe Coding.
Antoni Gmitruk - Spend time crafting the architecture and other details with an LLM before offloading it to an AI editor.
Vibe Coding Advice from Tom:
1. Pick Up the Tools: If you don't know a lot about programming start with Lovable or Replit. These tools give you a feel of the UI. And if you know how to write code (doesn't matter how good you are), you should try dabbling with tools like Windsurf or Cursor
2. Use Version Control Religiously: Once you have something you think is working, feel free to push to github. Do not rely on the LLM to revert the code for you because this is not always reliable
3. Write High Level Tests: Have your LLM write high level tests for your software so that you safeguard your application against unwanted changes by the LLM.
4. Bug Fixes: Sometimes, when you encounter an error message, just copy pasting the error stack is good enough for the LLM to solve it for you. For complex bugs, it's okay to reset after a failed attempt and starting over. Again, Github is your friend.
5. Documentation: You can download all the documentation for the framework you're working with and put it into a subfolder for the AI editor to access.
6. Choosing the tech stack: It's a safe bet to work with something that has been around for a long time and has a lot of open source code available.