sharing something I built that might be useful here.

It's an open-source CLI tool called AI SOV Analyzer. The idea: AI models like ChatGPT are increasingly where buyers discover products. This tool lets you measure how often your brand shows up in AI responses vs your competitors basically "Share of Voice" but for AI.

Free to run (works with Ollama locally or free-tier APIs)

Apache 2.0 open source

I've been talking to dozens of PMs over the last few weeks who prototype with Lovable, Bolt, Figma Make, V0, etc. Same frustrations keep surfacing.

• Output looks a bit generic: looks like a demo, not your actual product

• Context loss: explain your product in ChatGPT/Claude, then re-explain in Lovable, then again somewhere else

• No edge case thinking: AI executes prompts literally, doesn't challenge or expand on them

The core issue I keep seeing: these tools are interface builders. They're great when you already know exactly what to build. But the hard part, thinking through the flows, the states, the edge cases, where users will actually get stuck, that's still entirely on you.

Heya

I m thinking of building a simple, unbiased comparison platform for products, services, tools even technical stuff like frameworks, APIs, and AI tools to help you decide faster with clear side-by-side insights.

Personally, I often find myself deep in Amazon reviews, YouTube videos, and scattered blog posts when trying to choose something new. While some comparison sites exist, I ve never found a complete or truly comprehensive solution. The same goes for developers when exploring new frameworks or libraries with similar alternatives, a quick, focused comparison could really help clarify things.

Before going further, I d love to hear from you: Would you find this useful? Your feedback will help shaping what I build next.

It s the third week of working on my little side project, SimploMail.com, and to speed things up I ve been doing a lot of vibe coding. It s been fun, but a few things became obvious pretty quickly.
I stopped using the auto model setting in the IDE. When it silently switches models, the quality drops fast. I can feel when the agent all of a sudden looses its intelligence . So now I just pick one model I trust and stick with it.
I also try to keep each AI session focused on one small task. One feature, one change. After it writes the code, I go through everything myself. I check for hard coded config, make sure it didn't quietly delete a unit test to make something compile, and etc. Sometimes it does update unit test just to make it pass .
And I never commit without reviewing. The AI is helpful, but it can also remove something important without telling you. I've seen it happen enough times now .

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!

I am seeing this with Lovable, Verdent, Replit: I am clear, RAG my prompts, clean them with Claude Opus 4.6, find that with tough problems, they'll tell me something is fixed or done, and it isn't. Not even close. And I'm burning costly credits, making no progress.
I'd love to learn what others are doing.
I'm building a multi-agent tool that integrates with 25+ LCNC sites and also IDEs, and yes, there are tough problems with the tool's awareness of what a user is doing in a console or fields in a browser window. I'd apprecaite it if the nocode platform simplay told me, "no can do," rather than trying one thing after another, staying stuck, and costling me $100 or more per day to keep failing.
Thanks, in advance, for your suggestions!

Had a fascinating discovery call yesterday. Founder showed me their SaaS - built entirely with Cursor in one weekend. Stripe payments, auth, admin panel. Actually works great, they're at $11k MRR.

Then they opened the codebase.

Wherever you code (online, CLI, or IDE), everyone has some love, hate or horror vibe coding stories, from building a prod-ready app in minutes to the whole repo got wiped. Would love to hear your story.

I ve been using Pencil.dev for a few days and honestly it s a big paradigm shift for how fast you can explore UI. I'm loving it!!

One thing I bumped into: I still need to move some screens into Figma to polish details, collaborate, and keep everything in the same place as the rest of our design work.

On social media, we're constantly hearing about individuals who never knew how to code and were able to vibecode a product within a short period of time.

Whenever I come across these posts, I always wonder if their product is truly marketable and profitable. Or, they are just selling the dream.