So Corbin always stresses the importance of having a decent understanding of software terminology in order to be the director and not the writer of code/software anymore. I thought about using notebookLM and corbin's six hour plus video playlist to create a learning set of basic terminology. Now my Question. Is that enough, or should I add more sources to that? Because the playlist is not solely about basic terminology... its about teaching people how to vibe code

Hey vibers! I am trying to clean up the files from my project (just vibing) but cursor is telling this amount of lines are normal and want to keep them as it is, and if something is reduce like just by 100 lines, is this even worth it ? - package-lock.json — 5,122 lines - src/App_old.tsx — 2,376 lines - src/services/gemini.ts — 1,151 lines - src/components/features/camera/CameraModal.tsx — 773 lines

Hey everyone, I’m a student and after binge watching way too many videos during break about building AI websites, I finally finished my first MVP. I’d honestly really appreciate if anyone could take a look and tell me why it’s garbage or what’s confusing or missing. No ego attached, I’m just trying to learn and make it better. Thanks in advance 🙏 Pickkits.com

I discovered Conductor Extension for Gemini CLI and tried it out. Gemini 3.0 Pro Thinking told me that it likes the plan. I have also given it rules that I got from AICodeKing on YouTube that has it trained to do things that will keep it on track. Many times the AI hallucinates and does not even remember your tech stack. This will help on that. The features of the Conductor Extension is: Features - Plan before you build: Create specs and plans that guide the agent for new and existing codebases. - Maintain context: Ensure AI follows style guides, tech stack choices, and product goals. - Iterate safely: Review plans before code is written, keeping you firmly in the loop. - Work as a team: Set project-level context for your product, tech stack, and workflow preferences that become a shared foundation for your team. - Build on existing projects: Intelligent initialization for both new (Greenfield) and existing (Brownfield) projects. - Smart revert: A git-aware revert command that understands logical units of work (tracks, phases, tasks) rather than just commit hashes. I have it just reviewing my present codebase to see what is good and what needs help. In the last image you can see all the files it came up with about my codebase.

Hi guys: Just wanted to let you know. If you are not using this new feature in Cursor you are missing out. I've been using it lately and it catches the bug usually on the first test. Give it a shot! Don't waste time sending bugs in agent mode and the agent guessing and doing fixes that it thinks it can quickly fix. Of course if is something minor, that's fine. But for complex bugs give it a try. You won't regret it. 😊