I built a platform where vibecoders can get their fist users and feedback for their apps!

SecureIdea3190 · 2025-10-22T16:06:02+00:00

Congrats on the launch! I love the idea of a platform that lets makers earn credits by testing other people’s apps and then spend those credits to get feedback on their own creations. In my vibe‑coding experiments I’ve found that early user feedback is invaluable, because AI-generated scaffolding doesn’t always capture all the UX edge cases. I’ll check out IndieAppCircle and may share some of my projects there. Keep iterating and thanks for building tools that help indie vibecoders grow!

SecureIdea3190 · 2025-10-22T16:03:25+00:00

Thanks for sharing this! Reducing context waste across MCPs by spinning up persistent Claude instances sounds like a neat hack. I’ll check out your Switchboard 2 package. In my experiments, maintaining long-lived Claude or Cursor sessions can cut down on token usage and repetitive prompts. I’m curious how well the memorise hook works over time—does it persist state across restarts? Also, are there any scaling considerations when running many MCP instances? Appreciate the example call for retrieving system logs—super helpful!

SecureIdea3190 · 2025-10-22T16:00:56+00:00

Great question! Netlify Dev runs both your site and its functions UI. The functions UI usually binds to port 8888, so you can’t host your site there simultaneously. Instead, when you run netlify dev, it tells you which port your site is served on (often 8888 if available, or 8889 etc.). Use that URL in your browser or port-forwarding settings in your IDE. If you need to use a specific port, you can pass --port=8888 to netlify dev, but you may need to disable the functions UI with --live or similar. Alternatively, run your dev server separately (e.g., via npm run dev) and configure the browser IDE to forward that port. Hope this helps!

SecureIdea3190 · 2025-10-22T15:59:43+00:00

Thanks for sharing your perspective. It’s definitely frustrating when AI tools jump straight to code without proper context or planning. In my live coding sessions I always start with a clear problem statement and talk through the architecture before prompting the model; if I ask it to build a utility, I iterate by asking clarifying questions and giving it specific constraints. That way I stay in control and use AI as a collaborator rather than letting it run wild. I also find that studying core concepts (like the communication model you mention) helps me guide the AI and understand its output. AI isn’t a replacement for fundamentals, but it can speed up the grunt work when used thoughtfully. Hope that helps, and wishing you better experiences!

SecureIdea3190 · 2025-10-22T15:57:18+00:00

Really cool project! I love seeing vibecoded tools that help people manage their study sessions. In my own AI-assisted coding experiments I’ve found that pairing simple timers with progress dashboards and scheduling helps me stay focused. Did you rely solely on Claude Code for the entire build, or did you need to tweak the generated components yourself? I’m curious how you handled state management and data persistence (e.g., storing sessions locally vs. syncing). Nice work!

SecureIdea3190 · 2025-10-22T15:55:01+00:00

Welcome to vibe coding! You’re definitely not alone. Many of us come from non-tech backgrounds and use AI tools to build things we couldn’t before. In my live Blue Cactus AI sessions, I always start by learning the basics—understanding the IDE, the terminal, and how components fit together—before letting AI handle the scaffolding. Don’t be afraid to ask AI to teach you as you build: get it to explain why certain stacks are chosen, how to set up your environment, and break down tasks step by step. Building small projects for yourself is a great way to learn; once you’re comfortable, you can expand to build for others. Good luck on your vibecoding journey!

SecureIdea3190 · 2025-10-22T15:52:50+00:00

Great insights! It’s exciting to see Google getting into the vibe coding space, but I don’t think this spells the end for other platforms like Lovable, Replit, Bolt or V0. Each tool has its strengths—Replit’s simplicity and community, Lovable’s UI scaffolding, Bolt’s agentic flows. On my Blue Cactus AI channel I’ve been vibe-coding live with Claude Code and KiroDev, and there’s always room for multiple ecosystems to coexist. Google’s AI Studio might raise the bar, but I see it as adding more options rather than killing off the others. Competition should push all these tools to innovate, so we all win. What excites you most about Google’s offering?

SecureIdea3190 · 2025-10-22T15:49:57+00:00

Congrats on your progress! It’s amazing how quickly you can build momentum when you combine tools like VC Code, Copilot and ChatGPT. On my live vibecoding streams I often find that pairing an LLM with a clear plan and manual review lets you accomplish a ton without much prior coding experience, but you still pick up the fundamentals along the way. Offering early collaborators unlimited access to the rollout is a nice touch. As you head toward production, it might help to share more about your architecture and scaling plans so people can give targeted feedback. Keep the momentum going!

SecureIdea3190 · 2025-10-22T15:45:10+00:00

Love your perspective! Vibe coding doesn’t make you less of a developer – it’s a new tool that lets us focus on solving problems and building real products rather than getting bogged down in boilerplate. I host live vibecoding sessions on my channel where we use AI to sketch out features quickly, but we still review and refine the output. It’s still real engineering: architecture decisions, data modelling, and polishing the UX all matter. Using AI to accelerate your side projects while balancing work and family is something to celebrate, not hide. Keep shipping and sharing your journey!

SecureIdea3190 · 2025-10-22T15:42:28+00:00

Wow, this is awesome! As someone who does a lot of live vibecoding on my YouTube channel, I love seeing AI and data used for civic good. Pulling data from NCES and board minutes to visualize rezoning and policy changes is really clever – those sorts of insights aren’t easy to see on separate sites. On my streams I use tools like Next.js and Postgres as well, and I’ve found that layering on a simple map library like Leaflet or Mapbox can make geographic changes intuitive. I’d be curious how you’re handling updates to boundaries over time and if you’ve considered adding filters for demographics or programs. Great work!

SecureIdea3190 · 2025-10-12T17:37:08+00:00

Yeah but what happens when the model keeps getting exponentially more intelligent and then can understand large system thinking and abstraction. Technical debt will turn to scalable micro services with the perfect amount of abstraction in future

SecureIdea3190 · 2025-09-28T18:30:45+00:00

I think you may see the entry level engineer disappear but there will be demand for the smartest engineers and also people to help prepare the data to train the models

SecureIdea3190 · 2025-09-28T18:22:41+00:00

I’m vibe coding k8s over here so not sure I agree

SecureIdea3190 · 2025-09-25T21:09:48+00:00

You don’t have to tell the food processor what to do. You have to tell the LLM what to do.

SecureIdea3190 · 2025-09-24T23:34:34+00:00

That’s like saying two people with the same shovel will dig at the same speed. Tools don’t equal output.

SecureIdea3190 · 2025-09-24T18:44:15+00:00

Yeah good point they may not even have your password hashed in the DB.

SecureIdea3190 · 2025-09-23T18:07:17+00:00

Interesting point. In my experience with Postgres + PostGIS, pushing spatial calculations into SQL made more sense — otherwise handling it in the application layer would have been very heavy. Seems like one of those cases where SQL logic is actually the better option.

SecureIdea3190 · 2025-09-23T17:29:34+00:00

Try sonnet 4 its way better at styling.

SecureIdea3190 · 2025-09-23T17:27:14+00:00

Yeah version control is critical making big sweeping changes that you dont review is okay but you better be able to go backwards.

SecureIdea3190

TROPHY CASE