... have been trying vibe coding more lately Its crazy how fast you can go from an idea to something that actually works But getting the first version out is easy Making the code clean enough to keep building on is a different story I am still figuring out where vibe

... Vibe-coding is fun for me. I do not have to necessarily write all that big codes and pages manually as AI easily does that for me. But, I also realized that it is very important for me and you to know what code does that AI write. I personally feel that AI is good in assisting the work but entirely leaving it to AI and not even checking would be dangerous in near time if not now. AI makes ... ... mistakes, and those mistakes can be costly for humans who used them to code. For me, there were several instances happened where I just got into flow of vibe

... Maker community! I ve been experimenting with the "vibe coding" workflow lately, and there s something incredibly satisfying about building useful micro-tools using nothing but a single `index.html` file in VS

... frontend for a living, and lately i can tell almost instantly when an app was vibe-coded. same component library, same gradient cards, same spacing that's slightly off everywhere. the code works, it just all converges on one generic look. vibe

... implementation. Billing feels very different. So do permissions, data deletion, security checks, or anything where one slightly different interpretation can have an actual consequence. And once you start defining enough rules yourself, I am not even sure where vibe coding ends and AI-assisted development begins. For people shipping real products this way, what do you still let the AI decide? And what have you decided should always be deterministic, no matter how good the model gets? Comment from Shivangi ...

... have been observing numerous posts on social media about just vibe coding your applications and sell it to the client or launch it, People actually ignore the technicality of saas products. I just want to know from them - What about database and its schema, how are you going to store data? What about application security? What about if you have to just add a new button in your page, are you gonna just ask the AI by pasting the whole ... ... code? What about scalability of the application? Are you sure, your application is not breaking from anywhere? Vibe

... wanted to share a bit of my experience with vibe coding, because about a year and a half ago this project was basically just an idea. I train regularly and use an Apple Watch, but I kept feeling that my fitness data was scattered everywhere. One place for workouts, another for recovery, another for fasting or hydration, and lots of metrics without much help deciding what I should actually do next. So I started thinking about building my own workout ... ... where the AI-generated solution wasn't right. Sometimes fixing one thing broke another. Sometimes I realized that what I had asked for wasn't actually good UX in the first place. But that became part of the process. Vibe

... exactly what I needed. The line I draw: build if it gives you a competitive edge, rent if it's commodity infrastructure. Comment from Aleksandar Blazhev(@byalexai): @alexcloudstar  nice can you name some of the things you vibe coded for yourself? Comment from Aleksandar Blazhev(@byalexai): @rnagulapalle  nice to hear your perspective!! I guess this is the main issue. It's easy to build, it's hard to maintatin (you should at least check ... ... name of your best vibe

... developer onto the project. Someone who hadn't been in the chat history. Who didn't know the 47 prompts that shaped the architecture. And I realized: I couldn't explain how the codebase worked. The problem: When I vibe code, I'm in a conversation. The AI and I go back and forth. It suggests something, I correct it, it refines, we iterate. But all that context lives in chat history. Not in the code. The code works ... ... after each major AI session Using comments in the code to explain why , not just what Asking the AI to summarize its own design choices But honestly? It's slow. And it feels like it defeats the purpose of vibe

... everyone! I'm excited to share Gen Vibe , an AI-powered music generation platform I've been building. The idea started with a simple question: What if anyone could turn their lyrics into a complete song in just a few seconds? With Gen Vibe

... have to open Meta Ads Manager, write hooks, script a video, fight the algorithm, and potentially face total market indifference. All that high energy immediately tanks. It s slow, it s thankless, and it s uncomfortable. The brutal truth: Vibe Coding has made building so easy and addictive that we unconsciously use it as an excuse to procrastinate on distribution. We d rather stack a 12th feature in our safe space than go out and hunt for our first paying ... ... open my IDE unless I spent the exact same amount of hours on distribution the day before. 1 hour of dev = 1 hour of marketing (copywriting, scripting, analyzing acquisition channels). Code has zero value if nobody sees it. 2. "Vibe

... vibe coding aesthetic online is all 'just describe what you want and ship.' The actual best ones I know do something different. What I keep noticing: - They write longer specs and shorter prompts - They check the agent's plan before letting it execute - They commit small, review often, and roll back without ego - They treat the agent as a fast intern who needs clear briefs The 'just vibe

... Vibe coding is fantastic for getting something working fast - but there's always a point where it starts to struggle. For me it was when I tried to add proper auth to a project that didn't have it baked in from the start. The AI kept suggesting patches instead of a real solution, and eventually I was chasing one fix into the next. Curious if others have hit a similar wall. What was the first thing in your vibe

... Vibe coding is great until your product has real users. Then the "vibe

... Last summer, the idea for my SaaS, Xolora, started to take shape. Around the same time, the concept of vibe coding was blowing up. As a non-technical founder, it sounded like a dream come true. No coding experience? No problem, just let AI handle it. The beginning was incredibly promising. Using Emergent made me feel unstoppable. I was seeing my idea come to life. But then, reality hit. The moment the architecture required deeper complexity the magic completely faded ... ... spent days stuck in endless debugging loops, trying to explain to an AI errors that I didn t even understand myself. I was burning precious time, and honestly, the Vercel deployments and GitHub conflicts became a nightmare. The vibe

... analyzed hundreds of App Store rejections. The vibe coding era has made the problem dramatically worse. I want to share something that's been genuinely painful to watch as someone who's spent months deep in App Store compliance data and as someone who has had past issues with compliance for vibe

... architecture decision, every scalable practice, every multi-tenant layer. It was hard, but I always felt in control of the machine I was creating. Then the AI era arrived. In 2025, I started heavily exploring AI coding assistants and vibe coding. At first, it felt magical. Faster output. Cleaner UI. Less friction. It genuinely impressed me. So I leaned into it. But after about 6 months, I started noticing something uncomfortable. The application became harder to reason about. Logic became ... ... looked smart . I m lucky because I already had strong development foundations before AI arrived. Maybe it was just a temporary AI hangover for me. But I genuinely worry about non-developers and newer builders entering software through pure vibe

... started vibe coding last year. Built a thing, shipped it, then stared at a screen with no idea what to do next. ChatGPT gave me a textbook. My founder friend gave me vibes

... everyone! I love the concept of "vibecoding", getting into the flow, using AI to build fast, and focusing purely on the product. But for a lot of developers (especially in emerging markets like Indonesia), that vibe instantly dies when it's time to deploy. Suddenly, you are dealing with complex server setups, fighting DevOps configurations, or getting blocked because you don't have an international credit card to spin up a basic server. Deployment shouldn't ruin the vibe

... Over the last few weeks, I reviewed more than 15 vibe-coded fintech and startup-style web apps. The surprising part was this: Even when teams were using AI coding tools, security agents, framework defaults, and modern deployment platforms, I still kept finding serious external security gaps. Not always one-click hack type issues, but the kind of problems that slowly stack up into real risk: - exposed admin/login surfaces - weak or missing security headers - bad TLS/configuration issues - missing SPF, DKIM ... ... public - outdated services - sensitive files accidentally exposed - redirects and auth flows that were not properly hardened The pattern was clear: AI helps people ship faster, but it does not automatically make the infrastructure secure. A lot of vibe

... Personally, I consider software built by someone who truly knows how to program to be more honest. I see that person as someone with real skills and valid knowledge. Subjectively, I value software created by them more than something (vibe)coded by me, since I don t understand code very well. TL;DR: I value the vibecoded project from a software engineer more than a project vibecoded by a layman. What is your perspective on vibe

... promote our Product Hunt launch of Vibe Check today, we are offering free evaluations. We are looking for Vibe

... been spending more time vibe coding recently, and I ve started to question something I initially took for granted. Most of the conversation around vibe

... Apple is reportedly pushing back on AI vibe coding apps like @Replit and @Vibecode App , tools that let users create apps just by typing prompts. The issue isn t a new rule. Apple is enforcing an old one: Apps must be self-contained They can t download or run new code that changes functionality after review That s exactly what vibe

... months ago (like everyone else) I also got overwhelmed with all this vibe-coding happening around me, being a developer myself I got a little FOMO too I have personally built a bunch of tools using "pure" vibe