After rebuilding the same project three times because AI forgot my architecture, I got fed up and built @CodeRide (Beta) with my team.

The problem: AI code assistants lose track of your project between sessions. Every time I start coding with Cursor, Claude, or any AI assistant, I waste time re-explaining my codebase structure, architectural decisions, and coding patterns.

What we built: The project management tool for coding agents using MCP. Upload your project documentation or PRD, and CodeRide breaks it into optimized, fully contextual tasks ready for your AI agent.

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...

Recently I've worked with a group of non-corders trying to "vibe code" their apps with AI.
While knowing code is clearly not a must these days, it helps to get technical.
People who were familiar with basic software engineering concepts were 10x more likely to success and get better results.
So, with the hope of providing value to the non-coders people, I've created a quick roadmap for the basic terms and concepts you should be familiar with.

• Requirements: Building apps with AI is all about being able to clearly guide AI and express your app features and requirements.
  You need to be able to express those ideas and explain them as you d explain to a human developer. Think like a Technical Product Manager.

• Frontend: The face of your app.
  It's what your users see and interact with. It could be a website, a mobile app, or a desktop app. Most popular frontend libraries and frameworks are React, Next.js.

• UIs: They are the buttons, the forms, the modals, the tooltips, etc. In React, the UI is built with components. For design & styling, Tailwind CSS is the most popular library.
  For animations, Framer Motion is the most popular library.

• Packages & npm: Apps are not built from scratch.
  They are built on top of existing libraries and frameworks, like lego blocks.

  The most popular package manager is npm. For example, "react-hook-form" is a famous package that helps you build forms.

• Backend: The backend is the part of your app that runs on the server.

  It's where you store your data, your business logic.

  e.g: If you want to send an email, or process payments - this is where you'll do it.

  Vibe tip: Use minimal backends with serverless functions.

• Database: The database is where you store your data.

  It's where you store your users, your projects, your tasks, etc. Think of it as a big spreadsheet.

  I recommend using a database that is integrated with your frontend.

  For example: Fine, or Supabase.

• API: Real-life apps almost always need to integrate with other apps.

  For example: if you want to send email, or get weather data, or integrate with AI - it's all done through APIs.

• Hosting & Deployment: For your app to be accessible to the public, you need to host it.

  The code is usually hosted on GitHub, and deployed to platforms like Fine, Vercel, Netlify.

Finally, being comfortable with code is helpful - even if not a must.

AI often makes minor mistakes (like importing a wrong package), and if you re not afraid of reviewing code - you will get better results faster.

Currently playing around with @bolt.new after being inspired by @gabe and building a bunch of mini apps, mainly for fun. Haven't pushed any to production yet but so far I'm enjoying it bar the odd hiccup where I have to roll back a few times to fix a stubborn error.

I've also looked into @Lovable and it seems pretty cool but wanted to see what people had to say about it. Is there any reason to pick one over the other and which one have you settled on?

I've been having a lot of fun exploring AI and using tools like @Cursor, @bolt.new, @Lovable, and @Warp to learn how to build and make some apps for myself! I'm also noticing a tremendous amount of growth in folks creating their own apps using these same tools which has me wondering... if a company wanted to acquire someone's app or tool that was built via vibe coding, would it matter how it was built? Does the method of how it was built impact the valuation?
In my idealistic eyes, I'd like to think it doesn't. As an acquisition is often much more than just the tech but also the user base, brand, and even team behind the product. If anything I think that acquiring a product that has been "vibe coded" and putting them into capable engineering hands would only enhance the product...or a least make the code base cleaner.
I also believe that talent that is able to create stunning products with AI is currently a small percentage of folks, and that companies should be investing in acquiring that talent (either independently or via product acquisition) so that they can stay ahead in innovation while learning how to implement AI tools more efficiently in their orgs.
Very curious to hear what you all think!

I'm what you might call a gringo vibe coder.

No dev degree. No traditional background. Just me, Cursor, Claude, and AI... figuring things out together.

Rick Rubin said it best: "In the past, for music, you had to go to the conservatory and study for years... then when punk rock came along... if you had something to say, you could say it." He calls vibe coding the punk rock of coding.

about to Launch a product for creators after building for a few weeks to months.
Started as a way to get into vibe coding and just got real useful real quick lol.
But the goal is still that - mix my skills and knowledge as an engineer with the good parts of AI coding.
So i learned a few of what to need and have

• Claude.md file

• best coding practices section

• pretty heavy compartmentalization & file structure separation

• certain ways to prompt

• ask for implementation plan before telling it to code

But i feel like all i learned is about directing prompts - im wondering...

what are you guys finding are the best .md or deeper ai vibe coding tricks that are helping you save time? be more efficient? debug ai less or help it get it right the first time? whats your vibe code tips and tricks?

I work at an early stage startup and I'd estimate 70-80% of our codebase is vibe coded (510k lines). To be clear, it's not 1 shot "build this feature." More like, "implement get_slim_documents for Jira in the exact same way we did it for the Confluence connector."
Comfort with AI coding tools is actually something we gauge during interviews/work trials. Looking at our peer companies, it's exactly the same.
My hypothesis/assertion is that companies founded ~2022+ are fundamentally intertwined with "vibe coding." In 5 years, programming will connote vibe coding more than it will connote non-AI assisted work.
Am I crazy? Pigeon-holed in the SF startup world? Naive? Would love to hear more thoughts/diverse perspectives on this.

Hi, I m an app developer who s shipped many projects the old-school way (hand-coding) for over a decade. Recently AI tools have exploded - speeding up my production like crazy.

What s happening:

- Idea to MVP: Creators focus on ideas while AI writes most of the code.

Claude just shared this with me. "unrestricted push" - cannot get that to work. Anyone have workarounds?
Trying to get my claude/claude code productivity up, so I have Claude tasking claude code, and using the newly-updated desktop app.